HP XP P9000 Performance for Open and Mainframe Systems User Guide Abstract This guide describes and provides instructions for using HP XP P9000 Performance Monitor Software and HP XP P9000 Cache Residency Manager Software to configure and perform operations on HP XP P9000 disk arrays. The intended audience is a storage system administrator or authorized service provider with independent knowledge of HP XP P9000 disk arrays and the HP StorageWorks Remote Web Console.
© Copyright 2010, 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 overview.................................................................................8 Performance Monitor overview...................................................................................................8 Performance Control overview....................................................................................................8 Performance of high-priority hosts...........................................................................................
Usage rate of a data recovery and reconstruction processor.........................................................35 Usage rate of cache memory...................................................................................................35 Write pending statistics...........................................................................................................35 Access paths usage statistics....................................................................................................
Viewing Cache Residency information.......................................................................................77 Placing specific data into Cache Residency cache.......................................................................77 Placing LDEVs into Cache Residency cache................................................................................79 Releasing specific data from Cache Residency cache..................................................................
Resource usage and write-pending rate statistics..................................................................118 Parity groups, external volume groups, or V-VOL groups statistics............................................121 Volumes in parity/external volume groups or V-VOL groups statistics.......................................122 Volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU)...............................................................
Port tab of the Performance Control main window.....................................................................188 WWN tab of the Performance Control main window................................................................190 D Cache Residency GUI reference...............................................................195 Cache Residency window......................................................................................................195 Multi Set dialog box ..............................
1 Performance overview Unless specified otherwise, the term HP XP P9000 refers to the HP XP P9500 Disk Array. This chapter provides an overview of the Remote Web Console software products that enable you to monitor and manage the performance of the HP XP P9500 storage system. Performance Monitor overview Performance Monitor enables you to monitor your HP XP P9500 storage system and collect detailed usage and performance statistics.
Upper-limit control Using Performance Control you can limit the number of I/O requests from servers to the storage system as well as the amount of data that can be transferred between the servers and the storage system to maintain production server performance at the required levels. This practice of limiting the performance of low-priority host servers is called upper-limit control.
Prestaging occurs under any of the following circumstances: • When prestaging is performed using Cache Residency. • When the storage system is powered on. • When cache maintenance is performed. Figure 1 Cache Residency cache area NOTE: • If the Cache Residency cache area is accessed for I/O before the prestaging operation is complete, the data may not be available in cache at the first I/O access.
Table 1 Cache capacity requirements for CR priority mode Settings of priority mode Standard cache capacity Specified number of cache areas is 8,192 or less and the specified 16 GB capacity is 128 GB or less Specified number of cache areas exceeds 8,192 or the specified capacity exceeds 128 GB 32 GB 1 GB = 1,073,741,824 bytes Bind mode (read and write data) In bind mode the Cache Residency extents are used to hold read and write data for specific extents on volumes.
Table 2 Bind mode cache requirements (continued) System Type RAID Level or Volume Type Capacity Specifications Cache Residency Cache Requirement Cache segments needed per slot: 12 (slot capacity / cache segment capacity) = 198 KB = 12 cache segments Note: Even though a mainframe track is 56 KB, because cache is divided into 16.5 KB segments, it requires 4 segments. RAID 1 mainframe, or external volumes Slot capacity: 66 KB Cache segment capacity: 16.
2 About performance monitoring This topic presents an overview of Performance Monitor and Cache Residency. Monitoring storage system resources Performance Monitor enables you to monitor your storage system and collect detailed usage and performance statistics. If there is a decrease in storage system performance (for example, delayed host response times), Performance Monitor can help you detect the cause of the problem and resolve it.
NOTE: • If you access the Cache Residency area for input and output before the prestaging operation is performed from the SVP or Remote Web Console, the host may not be able to find data in the cache at the first I/O access after Cache Residency is configured. • To prevent the slow response time of the host I/O, the prestaging operation may be interrupted when the cache load is heavy.
Bind mode has the following advantages: • The accessibility of read data is the same as Cache Residency priority mode. • Write operations do not have to wait for available cache segments. • There is no back-end contention caused by destaging data. In Bind Mode, the total capacity of cache required is: standard cache + Cache Residency cache For more information about calculating case size for bind mode, see “Estimating cache size” (page 69).
Changing the mode without cache extension requires reconfiguring Cache Residency (for example, release the data from cache, and then place the data back in cache with the desired mode).
3 Interoperability of Performance Monitor and other products This chapter describes the interoperability of Performance Monitor and other products. Cautions and restrictions for monitoring • Storage system maintenance If the storage system is undergoing the following maintenance operations during monitoring, the monitoring data might contain extremely large values. • ◦ Adding, replacing, or removing cache memory. ◦ Adding, replacing, or removing data drives.
Cautions and restrictions for usage statistics • Usage statistics for the last three months (93 days) are displayed in long-range monitoring, and usage statistics for up to the last 15 days are displayed in short-range monitoring. Usage statistics outside of these ranges are deleted from the storage system. • In the short range, monitoring results are retained for the last 8 hours to 15 days depending on the specified gathering interval.
windows, the graph displays changes in the maximum, average, and minimum I/O rates in one minute. Performance Control applies upper limits and thresholds to the average I/O rate or the average transfer rate calculated every gathering interval. For example, in the following figures in which the gathering interval is 1 minute, if you set an upper limit of 150 I/Os to the port 1A, the highest data point in the line CL1-A in Graph 2 and the line Ave.(1 min) in Graph 3 is somewhere around 150 I/Os.
NOTE: • Continuous Access Synchronous: Performance Control monitors write I/O requests issued from initiator ports of your storage system. • When the remote copy functions: (Continuous Access Synchronous, Continuous Access Synchronous Z, Continuous Access Journal, and Continuous Access Journal Z) are used in your environment, Performance Control monitors write I/O requests issued from initiator ports of your storage system.
Changing the time setting of SVP If the monitoring switch function is performed, do not change the time setting of the SVP. If the time setting is changed, the following problems can happen: • Invalid monitoring data appears. • No monitoring data is collected. If the time setting of the SVP is changed, turn off the monitoring switch, and then turn on the switch. After that, obtain the monitoring data. For details about the monitoring switch, see “Starting monitoring” (page 28).
Figure 8 Graph 3: I/O rate displayed in Performance Monitor (the Detail check box is selected) NOTE: • Continuous Access Synchronous: Performance Control monitors write I/O requests issued from initiator ports of your storage system.
4 Monitoring WWNs This topic describes how to set up WWNs to be monitored. Viewing the WWNs that are being monitored To view the WWNs that are being monitored: 1. Display the Remote Web Console main window. 2. Select Performance Monitor in Explorer, and select Performance Monitor in the tree. The Performance Monitor window opens. 3. Select the Monitored WWNs tab to see the list of WWNs that are currently being monitored. Adding new WWNs to monitor To add new WWNs to monitor: 1.
4. Click Add New Monitored WWNs. The Add New Monitored WWNs window opens. 5. Specify the following information for each new WWN: • HBA WWN (required) Enter the 16-digit hexadecimal number. • WWN Name (optional) Enter the unique name to distinguish the host bus adapter from others. The WWN Name must be less than 64 characters and must consist of alphanumeric characters and at least one symbol. • Port (In Available Ports) In the Available Ports list select the port connected to the WWN.
4. Select the WWN to connect to the port, and click Add to Ports. The Add to Ports window opens. If you select a WWN to connect, select one WWN in the list. If you select multiple WWNs and click Add to Ports, an error occurs. 5. Select a port to connect in Available Ports, and then click Add. However, the ports of the mainframe system are not displayed in the list because they are not supported for Performance Monitor. The added WWN and the port are specified for the Selected WWNs. 6.
5 Monitoring CUs This topic describes how to set up CUs to be monitored. Displaying CUs to monitor To display the list of CUs to monitor: 1. Open the Remote Web Console main window. 2. Select Performance Monitor in Explorer and select Performance Monitor from the tree. 3. Open the Monitored CUs tab. View the list of CUs. Adding or removing CUs to monitor NOTE: When a CU is removed from monitoring, the monitor data for that CU is deleted.
1. 2. Display the Remote Web Console main window. Select Performance Monitor in Explorer, and select Performance Monitor in the tree. The Performance Monitor window opens. 3. 4. Open the Monitored CUs tab. Click Edit CU Monitor Mode. The Edit CU Monitor Mode window opens. 5. Click View CU Matrix in the Edit CU Monitor Mode window. The View CU Matrix window opens. The following CUs are displayed in the Monitored CUs window: 6.
6 Monitoring operation This topic describes how to start and stop the monitoring operation. Performing monitoring operations This topic describes how to start or stop the monitoring operation. • To start the monitoring operation, see “Starting monitoring” (page 28). • To stop the monitoring operation, see “Stopping monitoring” (page 28). Starting monitoring To start monitoring the storage system, start Performance Monitor and open the Edit Monitoring Switch window.
4. Click Disable in the Monitoring Switch field. The Sample Interval list is grayed out and becomes ineffective. 5. 6. Click Finish to display the Confirm window. Click Apply in the Confirm window to stop monitoring.
7 Setting statistical storage ranges This topic describes setting statistical storage ranges. About statistical storage ranges Performance Monitor collects and stores statistics for two time periods (ranges): short range and long range. The difference between the two ranges and the statistics they target are as follows: • Short range If the number of CUs to be monitored is 64 or less, statistics are collected at a user-specified interval between 1 and 15 minutes, and stored between 1 and 15 days.
5. Select Set Range or Use Real Time in the Time Range as the periods (ranges) for displaying statistics. If Long-Range is selected, you can specify only Set Range. If Short-Range is selected, you can select Set Range or Use Real Time. Performance Monitor saves the statistics obtained up to 1440 times in SVP. Therefore, you can estimate the storing period of statistics with “gathering interval multiplied by 1440.
8 Working with graphs This topic describes how to display statistical graphs. Basic operation Use Monitor Performance window to display graphs. 1. Display the Performance Monitor main window. 2. Select Performance Monitor in Explorer, and select Performance Monitor in the tree. The Performance Monitor window opens. 3. Click Monitor Performance in the Performance Monitor window. The Monitor Performance window opens. 4. 5.
you click the text link, the resources assigned to an MP blade of top 20 in usage rates are displayed on the detailed window. 12. To close the graph, click Delete Graph. Objects that can be displayed in graphs Set items to display graph in the Performance Objects field of the Monitor Performance window. The outline of target objects and monitoring data that can be displayed in graphs is shown in the following table. The monitoring data shows the average value of sampling interval.
Monitoring target object Monitoring data Write throughput (IOPS). Cache hit (%). Data transfer (MB/s). Response time (ms). Back transfer (count/sec). Drive usage rate (%). *1 LUN Total throughput (IOPS). Read throughput (IOPS). Write throughput (IOPS). Cache hit (%). Data transfer (MB/s). Response time (ms). Back transfer (count/sec). External Storage Data transfer of logical devices (MB/s). Response time of logical devices (ms). Data transfer of parity groups (MB/s).
Usage rate of a data recovery and reconstruction processor Function A data recovery and reconstruction processor (DRR) is a microprocessor (located on the DKAs and channel adapters) that is used to generate parity data for RAID 5 or RAID 6 parity groups. The DRR uses the formula "old data + new data + old parity" to generate new parity. If the monitor data shows high DRR usage overall, this can indicate high write penalty condition. Please consult your HP representative about high write penalty conditions.
Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows. 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 paths usage statistics Function An access path is a path through which data and commands are transferred within a storage system.
Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows.
Item on left side of Object field Item on right side of Object field Item on left side of Monitor Data field Item on right side of Monitor Data field Write Throughput (IOPS) Total Sequential Random CFW Parity Group* None Total Throughput (IOPS) Total Sequential Random CFW Read Throughput (IOPS) Total Sequential Random CFW Write Throughput (IOPS) Total Sequential Random CFW LUN* None Total Throughput (IOPS) Total Sequential Random CFW Read Throughput (IOPS) Total Sequential Random CFW Wri
Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows. 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 Port* None Data Trans. (MB/s) None WWN* WWN Data Trans. (MB/s) None Port Data Trans. (MB/s) None None Data Trans. (MB/s) Total Logical Device* Read Write Parity Group* None Data Trans.
Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows.
hit ratio for that time period is 30 percent. A higher write hit ratio implies higher processing speed because fewer data transfers are made between devices and the cache memory. Storing period Short-Range can be specified. Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows.
Back-end performance Function The back-end transfer can be monitored. The back-end transfer is the number of data transfers between the cache memory and the hard disk drive. The graph contains following information. • Cache to Drive The number of data transfers from the cache memory to hard disk drives.
Storing period Short-Range can be specified. Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows. 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* None Drive Usage Rate (%) None Parity Group* None Drive Usage Rate (%) None * Only information on internal volumes is displayed.
Storing period Short-Range can be specified. Selection of monitoring objects Select monitoring objects in Performance Objects field. The combination of items is shown as follows. 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* None Business Copy (%) None * Only information on internal volumes is displayed.
9 Changing display of graphs This topic describes how to change displaying of graphs. Graph operation Information displayed in the graph can be changed. The following operations can be performed: • Displayed items in the graph can be changed. For details, see “Changing displayed items” (page 45). • Displayed periods in the graph can be changed. For details, see “Changing a display period” (page 45) • New graphs can be added. For details, see “Adding a new graph ” (page 45).
1. Display graph in the Monitor Performance window. For details, see “Basic operation ” (page 32). 2. Click Add Graph. The Add Graph window opens. 3. Change displayed items in the information setting field at the left of the window. For details, see “Basic operation ” (page 32). 4. Click Add. Items are added in the Selected Objects field. 5. 6. If you want to delete the item, select the item and then click Remove. Click OK. The graph is added.
10 Performance Control operations This topic provides information and instructions for using Performance Control software to perform upper-limit control. Overview of Performance Control operations Procedures for using Performance Control depend on the connection between host bus adapters (HBAs) and storage system ports. HBAs are adapters contained in hosts and serve as host ports for connecting the hosts and the storage system.
1. Set priority to ports on the storage system using the Port tab of the Performance Control main window. In network A, the ports 1A and 1C are connected to high-priority production servers. The port 2A is connected to a low-priority development server. Therefore, the ports 1A and 1C should be given high priority, and the port 2A should be given low priority. The next figure shows a portion of the Performance Control main window where the abbreviation Prio.
3. Set an upper limit to traffic at the non-prioritized port. To prevent decline in I/O rates at prioritized ports, you set upper limit values to the I/O rate for non-prioritized ports. When you set an upper limit for the first time, it is recommended that the upper limit be approximately 90 percent of the peak traffic. In network A, the peak I/O rate for the non-prioritized port (2A) is 200 IO/s. So, the recommended upper limit for 2A is 180 IO/s.
Figure 13 Network B (many-to-many connections are established between HBAs and ports) If many-to-many connections are established between HBAs and ports, take the next steps: 1. Find WWNs of host bus adapters. Before using Performance Control, you must find the WWN (Worldwide Name) of each host bus adapter in host servers. WWNs are 16-digit hexadecimal numbers used to identify host bus adapters. For details on how to find WWNs, see the HP XP P9000 Provisioning for Open Systems User Guide. 2.
3. Set priority to host bus adapters using the WWN tab of the Performance Control main window. In network B, the production server is given high priority and the development server is given low priority. If your network is configured as in Figure 13 (page 50), you must give high priority to wwn01 and also give low priority to wwn02 and wwn03. To give priority to the three host bus adapters, take the following steps: • In the WWN tab, select one of the four ports that the HBAs are connected to (i.e.
Figure 16 Traffic at ports 5. Set an upper limit to traffic between ports and the non-prioritized WWN to prevent decline in I/O rates at prioritized WWNs. When you set an upper limit for the first time, the upper limit should be approximately 90 percent of the peak traffic level. In network B, the peak I/O rate at the paths between port 1A and the non-prioritized WWNs (wwn02 and wwn03) is 200 IO/s. The peak I/O rate at the paths between port 1C and the non-prioritized WWNs is also 200 IO/s.
If an upper limit of the non-prioritized WWN is set to zero or nearly zero, I/O performance might be lowered. If I/O performance is lowered, the host cannot be connected to the storage system in some cases. 7. If necessary, apply a threshold. If you want to use threshold control, set a threshold in the WWN tab in the Performance Control main window. In the WWN tab, you can specify only one threshold for the entire storage system, regardless of the number of prioritized WWNs.
For details on the system configuration of one-to-one connections between host bus adapters and ports, see “If one-to-one connections link HBAs and ports” (page 47). This topic explains operation procedures you can perform for ports and the entire storage system. Analyzing traffic statistics The traffic statistics reveal the number of I/Os that have been made via ports. The traffic statistics also reveal the amount of data that have been transferred via ports.
7. Right-click a low-priority port and then select Prio ->> Non-Prio from the pop-up menu. If there is more than one low-priority port, repeat this operation. The Attribute column displays Non-Prio. You must set upper limit values for the Non-prio. specified ports. For detail about the setting of upper limit values, see “Setting upper-limit values to traffic at non-prioritized ports” (page 55). 8. Click Apply. The settings on the window are applied to the storage system.
Setting a threshold If threshold control is used, upper limit control is automatically disabled when traffic between production servers and the storage system is reduced to a specified level. For details, see “Threshold control” (page 9) and “If one-to-one connections link HBAs and ports” (page 47).
Table 6 Relationship between the thresholds of the prioritized port and the upper limits of the non-prioritized port Thresholds settings A number other than zero is set to the upper limit of the non-prioritized port Zero is set to the upper limit of the non-prioritized port Threshold Is Set to When thresholds are set to multiple prioritized The threshold control of the prioritized The Prioritized port ports, depending on the transfer rate, following port is not executed. controls are executed.
2. 3. 4. 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 visible. The two trees are displayed in the left side of the WWN tab. The upper-left tree lists ports in the storage system. 5. 6. 7. Select All from the list at the top right corner of the window. In the upper-left tree, double-click a port. Double-click Non-Monitor below the specified port.
If you add a port or host bus adapter to the storage system after the settings above, the traffics about connections to the newly added port or host bus adapter will not be monitored. In this case, follow the procedure above again to make all the traffics between host bus adapters and ports monitored. Up to 32 host bus adapters (WWNs) can be monitored for one port.
2. 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. Select the WWN tab. Select All from the list at the top right corner of the window. Do one of the following: • To analyze I/O rates, select IOPS from the list at the upper left corner. • To analyze transfer rates, select MB/s from the list at the upper left corner of the list.
7. 8. Double-click Monitor, which is displayed below the specified port. Check to see if all the WWNs of the host bus adapters to be controlled by using Performance Control appear below Monitor. If some of the WWNs are missing, use the procedure in “Monitoring all traffic between HBAs and ports” (page 57) to move all WWNs to below Monitor. 9. Click Monitor to display the information of the host bus adapters that are monitored in the list on the right of the tree. 10.
3. 4. 5. 6. 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 bus adapters and storage system ports, you can set one threshold value for the entire storage system. In this environment, you cannot set individual threshold values for each prioritized WWN. 1. Click Reports > Performance Monitor> Performance Control to open the Performance Control window. 2. 3. 4. 5. 6. Click to change to Modify mode. In the Performance Control window, click Performance Control. The Performance Control main window appears.
7. 8. Enter a new PFC name in the PFC Name box and then select OK. You can use up to 64 characters for an PFC name. In the Performance Control main window, click Apply. The settings in the window are applied to the storage system. Registering a replacement host bus adapter If a host bus adapter fails, replace the adapter with a new one. After you finish replacement, you will need to delete the old host bus adapter from the Performance Control main window and then register the new host bus adapter.
Grouping host bus adapters Use Performance Control to create an PFC group to contain multiple host bus adapters. You can include a maximum of 32 host bus adapters in a PFC group. You can create up to 512 PFC groups in the storage system. All the host bus adapters (HBAs) in one PFC group must be of the same priority. Prioritized WWNs and non-prioritized WWNs cannot be mixed in the same group. You can use an PFC group to switch priority of multiple HBAs from prioritized to non-prioritized, or vice versa.
4. Select the WWN tab. 5. In the lower-left tree, double-click the PFC group ( deleted. 6. 7. Below the PFC icon, right-click the icon the host bus adapter ( Select Delete WWN from the pop-up menu. ) that contains the host bus adapter to be ) you want to delete. The selected host bus adapter icon is deleted from the tree. 8. Click Apply. The settings on the window are applied to the storage system.
6. If you selected the Storage System folder, take the following steps: • Select IOPS or MB/s from the list at the upper-left corner of the list. Select IOPS if you want to assign an upper limit to the I/O rate. Select MB/s if you want to assign an upper limit to the transfer rate. • To assign an upper limit to the I/O rate, enter the upper limit value in the IOPS column of the list. To assign an upper limit to the transfer rate, enter the upper limit value in the MB/s column of the list.
8. In the Performance Control main window, click Apply. The settings in the window are applied to the storage system. Deleting an PFC group 1. Click Reports > Performance Monitor> Performance Control to open the Performance Control window. 2. 3. Click to change to Modify mode. In the Performance Control window, click Performance Control. The Performance Control main window appears. Select the WWN tab. 4. 5. 6. 7. 68 In the lower-left tree, select and right-click an PFC group ( ).
11 Estimating cache size This topic describes how to estimate the cache size required for using Cache Residency. About cache size The required cache size for using Cache Residency differs according to operation modes or RAID levels. For example, if the bind mode is set, RAID1 storage systems require twice the size of cache for the user data to use Cache Residency. However, RAID5 or RAID6 storage systems require three times the size of cache.
If the priority mode or the bind mode is set, the cache size is calculated assuming that one slot has the following values. • • For open-systems volumes: ◦ For OPEN-V, one slot is 264 KB (512 LBAs). ◦ For other than OPEN-V, one slot is 66 KB (128 LBAs). For mainframe (3390) volumes: ◦ One slot is 66 KB (128 LBAs).
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 LBA ÷ 512) Round up the value that is calculated from the formula enclosed by ceil(). Converted value of starting address = 0 Converted value of ending address = (Number of slots × 512) - 1 2.
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. Number of addresses = Number of slots × 128 Convert the number of slots with 128 LBA. 3. Calculate the required cache size according to the operation modes, or the RAID levels to use Cache Residency. 1.
Calculating cache size for mainframe systems 1. Calculate the converted values of the starting address and the ending address. 1. For all specified LDEVs: Setting value of ending address (CC) = floor (((LDEV size × 15) - 1) ÷ 15) Round down the value that is calculated from the formula enclosed by floor(). "Setting value of ending address (CC)" is the value which is input on the Cache Residency window.
• For OPEN-V volumes, Cache Residency cache areas must be 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. If the remaining cache memory is less than 256 MB, Cache Residency is not available.
12 Managing resident cache This topic provides instructions for using Cache Residency software to manage resident cache. Cache Residency rules, restrictions, and guidelines Rules • Cache Residency must be enabled on Remote Web Console. • Administrator or Cache Residency write access to the Remote Web Console software is required to perform Cache Residency operations. Users without write access can view Cache Residency information for the connected storage system but cannot set or change options.
The following operations automatically reset Cache Residency cache: ◦ When LDEVs that is partly or wholly assigned to Cache Residency is deleted. ◦ When the parity group containing LDEVs that are assigned to Cache Residency is deleted.
If the host timeout period is set to 11 seconds or longer, limit the total amount of data to: ◦ 3 GB or less for open systems ◦ 3,000 cylinders or less for mainframe systems Launching Cache Residency 1. 2. Log on to the primary SVP. On the menu bar of the Remote Web Console main window, click Actions > Other function > Cache Residency. 3. In the Cache Residency window, change from View to Modify mode.
3. Select an unallocated area in the LDEV information table as the area to place specific data from one or more LDEVs into Cache Residency 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. 4.
7. 8. 9. Verify the Prestaging setting: • To enable prestaging, select Prestaging. • To disable prestaging, clear Prestaging. To start the operations, click Apply. If Prestaging was selected, respond to the Yes/No confirmation. To continue with prestaging, click Yes. To continue without it, click No. Monitor the Cache Residency window to make sure that the operations complete successfully. The cache information area shows the progress of the requested operations.
8. Monitor the Cache Residency window to make sure that the operations complete successfully. The cache information area shows the progress of the requested operations. Releasing specific data from Cache Residency cache This procedure releases specific data areas on one or more LDEVs from Cache Residency cache. 1. In the Cache Residency window, select the desired CLPR from the CLPR list. 2. In the CU:LDEV tree, select the LDKC and the CU containing the desired LDEV, and then select the desired LDEV.
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. 4. Repeat steps 2 and 3 until all desired operations are listed. NOTE: 5. 6. 7.
13 Troubleshooting This topic provides references to sources of troubleshooting and contact information for HP Technical Support. Troubleshooting resources For troubleshooting information on the XP P9500, see the HP XP P9000 Owner Guide. For troubleshooting information on the Remote Web Console software, see the HP XP P9000 Remote Web Console User Guide. For information on Remote Web Console error codes, see the HP XP P9000 Remote Web Console Messages.
14 Support and other resources Contacting HP For worldwide technical support information, see the HP Support Center: http://www.hp.
Conventions for storage capacity values XP P9000 disk arrays use the following values to calculate physical storage capacity values (hard disk drives): • 1 KB (kilobyte) = 1,000 bytes • 1 MB (megabyte) = 1,0002 bytes • 1 GB (gigabyte) = 1,0003 bytes • 1 TB (terabyte) = 1,0004 bytes • 1 PB (petabyte) = 1,0005 bytes • 1 EB (exabyte) = 1,0006 bytes XP P9000 disk arrays use the following values to calculate logical storage capacity values (logical devices): • 1 KB (kilobyte) = 1,024 bytes • 1 MB
CAUTION: IMPORTANT: NOTE: TIP: Indicates that failure to follow directions could result in damage to equipment or data. Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts.
A Export Tool This topic explains how to export the monitoring data collected on your storage system into files. About the Export Tool Use the Export Tool to export the monitoring data (statistics) shown in the Monitor Performance window to text files. You can also use the Export Tool to export monitoring data on remote copy operations performed by Continuous Access Synchronous, Continuous Access Synchronous Z, Continuous Access Journal, and Continuous Access Journal Z.
NOTE: If a firewall exists between the Remote Web Console computer and the SVP, see Chapter 2 of the HP P9000 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. • The Java Runtime Environment (JRE) To be able to use the Export Tool, you must install Java Runtime Environment on your Windows or UNIX system.
4. 5. Go to the /program/monitor/UNIX directory on the CD-ROM, and copy the export.tar file to the new directory you just created. Decompress the export.tar file on your system. The Export Tool is installed into the installation directory. Using the Export Tool To be able to export monitoring data, you must first prepare a command file and a batch file, and then you can run the Export Tool to export monitoring data.
The login subcommand logs the specified user into SVP. You must include the login subcommand in your command file. For detailed information about the login subcommand, see “login” (page 98). CAUTION: When you write the login subcommand in your command file, you must specify a user ID that should be used exclusively for running the Export Tool. See “System requirements” (page 86) for reference.
the stored data. You can specify both the short-range and long-range subcommands at the same time. The difference between these subcommands is as follows: ◦ The short-range subcommand is valid for monitoring data in short range. You can use this subcommand to narrow the export-target term for all the monitoring items you can specify by the group subcommand. Specify a term within "Short Range From XXX To XXX" which is output by the show subcommand.
Preparing a batch file A batch file is used to run the Export Tool. The Export Tool starts and saves monitoring data in files when you execute the batch file. The installation directory for the Export Tool contains two default batch files: runWin.bat for Windows systems, and runUnix.bat for UNIX systems. The following examples illustrate scripts in the runWin.bat and runUnix.bat batch files. These batch files include a command line that executes a Java command.
-Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain pause Example batch file for UNIX systems (runUnix.bat): #! /bin/sh java -classpath "./lib/JSanExport.jar:./lib/JSanRmiApiEx.jar:./lib/JSanRmiServerUx.jar" -Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain In the above scripts, and indicates the end of a command line.
Processing time Files saved by the Export Tool are often very large. The total file size for all the files can be as large as approximately 2 GB. For this reason, the exporting process might take a lot of time. If you want to export statistics spanning a long period of time, it is recommended that you run the Export Tool multiple times for different periods, rather than run it one time to export the entire time span as a single large file.
In the previous scripts, indicates the end of a command line. Log files When the Export Tool runs, the Export Tool creates a new log file on your system. Therefore, if you run the Export Tool repeatedly, the size of free space on your system will be reduced. To secure free space on your system, you are strongly recommended to delete the Export Tool log files regularly. For details about the location of the log files, see “Java” (page 116).
Error message ID Cause of error 5205 2003 An internal process is being executed, or maintenance is in progress. 5205 2033 SVP is now updating the statistics data. 5305 2033 SVP is now updating the statistics data. 5305 8002 The storage system status is invalid. Export Tool command reference This topic provides the syntax of the Export Tool subcommands that you can write in your command file and the command that should be used in your batch file.
Writing a script in the command file When you write a script in your command file, be aware of the following: • Ensure that only one subcommand is used in one line. • Empty lines in any command file will be ignored. • Use a semicolon (;) if you want to insert a comment in your command file. If you enter a semicolon in one line, the remaining characters in that line will be regarded as a comment.
Operands Operand Description ip-address Specifies the IP address of SVP. If SVP is managed with IPv6 (Internet Protocol Version 6), you must specify the ip-address operand to match the format of IPv6. If the Export Tool runs on Windows XP, the interface identifier (for example, "%5") must be added to the end of the specified IP address. host-name Specifies the host name of SVP. Alphanumeric characters, hyphen, and period can be specified. Underscore (_) cannot be specified.
login Description This e subcommand uses a user ID and a password to log the specified user in SVP. The svpip subcommand must execute before the login subcommand executes. The login subcommand fails if monitoring data does not exist in SVP. Syntax login userid password Operands Operand Description userid Specifies the user ID for SVP. If the user ID includes any non-alphanumeric character, the user ID must be enclosed by double quotation marks (").
Syntax show Outputs The show subcommand displays the storing period and the gathering interval for these two types of monitoring data: in short range and in long range. For example, the show subcommand outputs the following information: Short Range From: 2012/10/01 01:00 - To: 2012/10/01 15:00 Interval: 1min. Long Range From: 2012/09/01 00:00 - To: 2012/10/01 15:00 Interval: 15min. Short Range indicates the storing period and gathering interval of the monitoring data stored in short range.
Table 10 Operands of the group subcommand and saved monitoring data Operand GUI operation Monitoring data saved in the file Saved ZIP file PhyPG Select Parity Groups from Object list in Performance Objects field in Monitor Performance window. Usage statistics about parity groups PhyPG_dat.ZIP PhyLDEV Select Logical Device from Object list in Performance Objects field in Monitor Performance window. Usage statistics about volumes PhyLDEV_dat.
Table 10 Operands of the group subcommand and saved monitoring data (continued) Operand GUI operation Monitoring data saved in the file Saved ZIP file See RCLU_dat.
Table 10 Operands of the group subcommand and saved monitoring data (continued) Operand GUI operation Monitoring data saved in the file Saved ZIP file See 1 When you specify the PhyPG, PhyLDEV, PhyProc, or PhyESW operand, you can select the storing period of the monitoring data to be exported from short range or long range. When you specify other operands, the monitoring data in short range is exported. 2 A ZIP file name beginning with PhyExLDEV_. 3 A ZIP file name beginning with RCLDEV_.
Operand Description You can use the Short or Long option to select the storing period of the monitoring data to be exported. If you specify Short, the exported file will contain statistics in a short range for up to 15 days. If you specify Long, the exported file will contain statistics in a long range for up to three months (for example, up to 93 days). If neither Short nor Long is specified, statistics in both the short and long range are exported.
Operand Description PhyProc[Short|Long] Use this operand when you want to export the following statistics, which are displayed in the Monitor Performance window: • Usage rates of MPs • Usage rates of DRRs (data recovery and reconstruction processors) When statistics are exported to a ZIP file, the file name will be PhyProc_dat.ZIP. For details on the statistics exported by this operand, see Table 12 (page 118).
Operand Description exg-id is an ID of an external volume group.-volume-group-id is a migration volume group ID. You can check to which V-VOL group each LDEV belongs in the Basic Information Display dialog box (a Remote Web Console secondary window). The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. V1-1:V5-1 indicates V-VOL groups from V1-1 to V5-1. X1-1:X5-1 indicates V-VOL groups from X1-1 to X5-1.
Operand Description When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported. port-name is a port name. host-group-id is the ID of a host group (that is, a host storage domain). The host group (host storage domain) ID must be a hexadecimal numeral. The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from the host group #01 of the CL1-C port to the host group #03 of the CL1-C port.
Operand Description If port-name.host-group-id is not specified, the monitoring data of all the volumes (LUs) will be exported. RCLDEV[LDKC-CU-id]:[LDKC-CU-id][…]| Use this operand when you want to export statistics about remote copy operations which are displayed in the Usage Monitor tab in the Cnt Ac-S and Continuous Access Synchronous Z window.
Operand Description URLDEV Use this operand when you want to export statistics about remote copy operations which are [LDKC-CU-id]:[LDKC-CU-id][…] displayed in the Usage Monitor tab in the Cnt Ac-J and Cnt Ac-J Z window. 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.
The following example exports statistics about LU paths for the host group (host storage domain) ID 01 for the port CL1-A: group LU CL1-A.01:CL1-A.01 Short-range Description Use this subcommand to specify a term of monitoring data to be exported into files. Use this subcommand when you want to narrow the export-target term within the stored data. The short-range subcommand is valid for monitoring data in short range.
Operand Description Subtracts time from the ending time for collecting monitoring data, if yyyyMMddhhmm is omitted. If the last two digit of the time on the left or right of the colon (:) is not a multiple of the sampling interval, the time will automatically be changed so that the last two digits is a multiple of the sampling interval. If this change occurs to the time on the left of the colon, the time will be smaller than the original time.
long-range Description The long-range subcommand is used to specify a monitoring term (time range) for collecting monitoring data to be exported into files. Use this subcommand when you want to narrow the export-target term within the stored data. The long-range subcommand is valid for monitoring data in long range. The monitoring data in long range is the contents displayed in the Physical tab of the Performance Management window with selecting long-range as the storing period.
Operand Description Note: When you specify the ending date and time, make sure to specify a time that is at least 30 minutes before the current time. If you specify a time that is less than 30 minutes before the current time, the Out of range error might occur. +ddhhmm Adds time (ddhhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 201201120000+010130 indicates Jan. 13, 2012. 01:30. Adds time to the starting time for collecting monitoring data, if yyyyMMddhhmm is omitted.
outpath Description The outpath subcommand specifies the directory to which monitoring data will be exported. Syntax outpath [path] Operands Operand Description path Specifies the directory in which files will be saved. If the directory includes any non-alphanumeric character, the directory must be enclosed by double quotation marks ("). If you want to specify a back slash (\) in the character string enclosed by double quotation marks, repeat the back slash twice for example, \\.
Example The following example saves monitoring data in CSV files, not in ZIP files: option nocompress apply Description The apply subcommand saves monitoring data specified by the group subcommand into files. The login subcommand must execute before the apply subcommand executes. The apply subcommand does nothing if the group subcommand executes. The settings made by the group subcommand will be reset when the apply subcommand finishes.
Operands Operand Description switch={m|off} To start monitoring, specify the gathering interval (interval of collecting statistics) of monitoring data at m. Specify a value between 1 and 15 in minutes. m is the gathering interval in short range monitoring by Performance Monitor. The gathering interval in long range is fixed to 15 minutes. To end monitoring, specify off. If this operand is omitted, the set subcommand does not make settings for starting or ending monitoring.
Java Description This command starts the Export Tool and exports monitoring data into files. To start the Export Tool, write this Java command in your batch file and then run the batch file. Syntax Java -classpath class-pathrproperty-parameters sanproject.getmondat.RJMdMain Operands Operand Description class-path Specifies the path to the class file of the Export Tool. The path must be enclosed in double quotation marks ("). property-parameters You can specify the following parameters.
Operand Description Examples The following example assumes that the system running the Export Tool communicates with the SVP via a proxy host. In the following example, the host name of the proxy host is Jupiter, and the port name of the proxy host is 8080: java -classpath "./lib/JSanExport.jar;./lib/JSanRmiApiEx.jar; ./lib/JSanRmiServerUx.jar" -Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Xmx536870912 -Dmd.command=command.txt -Dmd.rmitimeout=20 -Dmd.logpath=log sanproject.getmondat.
Table 11 Performance management windows and monitoring data saved by the Export Tool (continued) GUI operation Monitoring data Select Cache from Object list in Performance Objects field in Monitor Performance window. “Resource usage and write-pending rate statistics” (page 118) Select Controller from Object list in Performance Objects field in Monitor Performance window.
Table 12 Files with resource usage and write pending rate statistics (continued) ZIP file CSV file Data saved in the file PHY_ExG_Trans.csv If external storage volumes are mapped to the volume groups of P9500, this file includes the amount of transferred data for volume groups including external storage volumes (KB/sec). PHY_ExG_Read_Response.
Table 12 Files with resource usage and write pending rate statistics (continued) ZIP file PhyESW_dat.ZIP CSV file Data saved in the file PHY_Long_DRR.csv Usage rates for DRRs (data recovery and reconstruction processors) in long range. PHY_Short_DRR.csv Usage rates for DRRs (data recovery and reconstruction processors) in short range. PHY_Long_CHA_ESW.csv Usage rates for access paths between channel adapters and cache memories in long range PHY_Long_DKA_ESW.
Parity groups, external volume groups, or V-VOL groups statistics The following table shows the file names and types of information in the Monitor Performance window that can be exported to files using the Export Tool. These files contain statistics about parity groups, external volume groups, or V-VOL groups. Table 13 Files with statistics about parity groups, external volume groups or V-VOL groups ZIP file CSV file Data saved in the file PG_dat.ZIP PG_IOPS.
Table 13 Files with statistics about parity groups, external volume groups or V-VOL groups (continued) ZIP file CSV file Data saved in the file PG_Read_Response.csv Average read response time (ms) at parity groups, external volume groups, or V-VOL groups PG_Write_Response.csv Average write response time (ms) at parity groups, external volume groups, or V-VOL groups NOTE: The parity group number is output in the column header of each performance value in these files.
Table 14 Files with statistics about volumes in parity / external volume groups, or in V-VOL groups (continued) ZIP file CSV file Data saved in the file LDEV_dat/LDEV_C2D_Trans.ZIP LDEV_C2D_Trans_x-y.csv The number of data transfer operations per second from cache memories and hard disk drives (for example, volumes) LDEV_dat/LDEV_D2CS_Trans.ZIP LDEV_D2CS_Trans_x-y.
Table 15 Files with statistics about volumes in parity groups, external volume groups, or V-VOL groups (at volumes controlled by a particular CU) (continued) ZIP file CSV file Data saved in the file LDEVEachOfCU_dat/LDEV_Write_IOPS.ZIP LDEV_Write_IOPSxx.csv The number of write operations per second LDEVEachOfCU_dat/LDEV_Seq_Write_IOPS.ZIP LDEV_Seq_Write_IOPSxx.csv The number of sequential write operations per second LDEVEachOfCU_dat/LDEV_Rnd_Write_IOPS.ZIP LDEV_Rnd_Write_IOPSxx.
Table 16 Files with statistics about ports ZIP file CSV file Data saved in the file Port_dat.ZIP Port_IOPS.csv The number of read and write operations per second at ports Port_KBPS.csv The size of data transferred per second at ports (KB/sec) Port_Response.csv The average response time (microseconds) at ports Port_Initiator_IOPS.csv The number of read and write operations per second at Initiator/External ports Port_Initiator_KBPS.
Table 18 Files with statistics about volumes (LUs) (continued) ZIP file CSV file Data saved in the file 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.csv The read hit ratio in sequential access mode LU_Rnd_Read_Hit.csv The read hit ratio in random access mode LU_Seq_Write_Hit.csv The write hit ratio in sequential access mode LU_Rnd_Write_Hit.
Table 20 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.
Table 22 Files with statistics about remote copy operations by Cnt Ac-S and Cnt Ac-S Z (for each volume (LU)) ZIP file CSV file Data saved in the file RCLU_dat.ZIP RCLU_All_RIO.csv The total number of remote I/Os (read and write operations) RCLU_All_Read.csv The total number of remote read I/Os RCLU_All_Write.csv The total number of remote write I/Os RCLU_RIO_Error.csv The number of errors that occur during remote I/O RCLU_Initial_Copy_RIO.
Table 23 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_RIO_Error.ZIP RCLDEV_RIO_Error_xx.csv The number of errors that occur during remote I/O RCLDEV_dat/RCLDEV_Initial_Copy_RIO.ZIP RCLDEV_Initial_Copy_RIO_xx.csv The number of initial copy remote I/Os RCLDEV_dat/RCLDEV_Initial_Copy_Hit.ZIP RCLDEV_Initial_Copy_Hit_xx.
contain statistics about remote copy operations (whole volumes) by Continuous Access Journal and Continuous Access Journal Z. Table 24 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J Z (In the whole volumes) ZIP file CSV file Data saved in the file UniversalReplicator.zip UniversalReplicator.csv The following data in the whole volumes are saved: • The number of write I/Os per second.
Table 25 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J Z (at journals) (continued) ZIP file CSV file Data saved in the file URJNL_R-JNL_Asynchronous_Journal.csv The number of journals at the secondary storage system URJNL_R-JNL_Asynchronous_Copy_Transfer.csv The average transfer rate (KB/sec) for journals in the secondary storage system URJNL_dat.ZIP URJNL_R-JNL_Asynchronous_Copy_Response.
Table 27 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J Z (at Volumes controlled by a particular CU) (continued) ZIP file CSV file Data saved in the file URLDEV_dat/URLDEV_Write_Hit.ZIP URLDEV_Write_Hit_xx.csv The number of write hit records per second URLDEV_dat/URLDEV_Read_Transfer.ZIP URLDEV_Read_Transfer_xx.csv The amount of data that are read per second (KB/sec) URLDEV_dat/URLDEV_Write_Transfer.ZIP URLDEV_Write_Transfer_xx.
Invalid values of monitoring data Probable causes The monitoring data in the CSV The value (-4) indicates that Performance Monitor failed to obtain monitoring data file includes (-4). for the following reason: If the period for the monitoring data that is specified with the Export Tool does not match the collecting period for monitoring data, the Export Tool cannot collect the monitoring data.
Possible problems Probable causes and recommended action If the error message ID is (0002 5510), probable error causes and solutions are: • An internal processing is being performed in the disk array. Alternatively, another user is changing configurations. Wait for a while and then run the Export Tool again. • Maintenance operations are being performed on the disk array. Wait until the maintenance operations finish and then run the Export Tool again.
Export Tool messages Probable causes and recommended action Invalid value: "value" The specified value is invalid. Specify a correct value. Login failed An attempt to log into SVP failed. Probable causes are: 1. An incorrect operand is used for the svpip subcommand. 2. An incorrect operand is used for the login subcommand. 3. The specified user ID is used by another person, and the person is being logged in. 4.
Export Tool messages Probable causes and recommended action RMI server error (part-code, error-number) An error occurs at the RMI server. For detailed information, see the HP P9000 Remote Web Console Messages. Unable to display help message The Export Tool cannot display the online help due to a system error. Unable to get serial number The Export Tool cannot obtain the serial number due to a system error. Unable to get time range for monitoring SVP does not contain monitoring data.
B Performance Monitor GUI reference This topic provides reference information about the Performance Monitor GUI. Performance Monitor main window • “Summary” • “Monitored CUs tab” • “Monitored WWNs tab” This is the main window for monitoring performance on your storage system. From this window you can set up monitoring parameters, start and stop monitoring, and view performance graphs. This window is available when Performance Monitor is selected in the Remote Web Console main window.
Summary The summary information of monitoring is displayed. Item Description Monitoring Switch Monitoring statuses of following: Enabled: Performance Monitor is monitoring the storage system. Disabled: The storage system is not being monitored. Sample Interval Current sampling interval, from 1 to 15 minutes, for which statistics are collected during short-range monitoring. This value is available when Enabled is selected in the Monitoring Switch field. If Disabled is selected, a hyphen appears.
Item Description 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. Edit WWN Click to open the Edit WWN window. Delete Unused WWNs* Click to open Delete Unused WWNs window. Add to Ports* Click to open the Add to Ports window.
Confirm window Use this window to confirm the specified monitoring information and to assign a task name to the editing task. Monitoring Switch Setting table Confirm the monitoring switch information to be changed. Item Description Monitoring Switch Following monitoring statuses of the storage system. Enable: Performance Monitor is monitoring the storage system. Disable: Performance Monitor is not monitoring the storage system. Sample Interval Time interval of collecting statistics.
Data Range Specify a range of statistics. Short-Range is default when there is monitor data collected with Short-Range. However, Long-Range is default when there is no monitor data collected with Short-Range. • Short-Range: Graphs are displayed according to the value specified in the Sample Interval field in the Edit Monitoring Switch window. • Long-Range: Graphs are displayed 0, 15, 30, or 45 minutes on every hour.
Item Description For details, see “Object and Monitor Data combinations”. Performance Object Selection: Objects that can be displayed in graphs. For details, see “Available Objects table”. Add Adds objects to display the graph. 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. • If Controller is selected on the left side of the Object field, the item on the right side of Monitor Data field is blank.
Item on right side of Object field • Item on left side of Monitor Data field Unit of monitoring data Data Trans. MB/s Response Time ms If Logical Device is selected on the left side of the Object field, the item on the right side of the Object field is blank.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Drive Access Rate* Read (Sequential) % Read (Random) Write (Sequential) Write (Random) Business Copy* None % *Only information about internal volumes is displayed. Information about external volumes and FICON DM volumes is not displayed. • 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.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) Drive Usage Rate* None % *Only information about internal volumes is displayed. Information about external volumes and FICON DM volumes is not displayed. • If LUN is selected on the left side of the Object field, the item on the right side of the Object field is blank.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) • 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.
Monitoring object Item Description HBA WWN WWN of the host bus adapter. A WWN is a 16-digit hexadecimal number used as the unique identifier for a host bus adapter. WWN Name Nickname of the host bus adapter. A WWN name is up to 64 alphanumeric characters and some signs. LDEV ID 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.
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. Remove Click to remove CUs from Monitored CUs table. Monitored CUs table A table of the CUs that are going to be monitored. Item Description CU 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.
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.
Selected CUs to Disable Monitor table Information about the CUs not to be monitored. Item Description CU CUs not to be monitored. Number of LDEVs Number of LDEVs in the CU not 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.
Item Description 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: Monitored CUs Set Monitored CUs Release Monitored CUs Total count of monitored CUs. Cell marker indicating that a CU is being monitored. Cell marker indicating that the CU is scheduled to be monitored. Cell marker indicating that the CU is scheduled to be released from monitoring. Close Closes this window. Help Opens the help topic for this window.
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. OK Click to select CUs of the parity group. When you select a parity group and click OK, CUs of the parity group are selected in the Unmonitored CUs table. Cancel Cancels this operation and closes this window.
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. Close Closes this window. Help Opens the help topic for this window. Edit WWN wizard 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.
Monitored WWNs table Confirm the information about the WWNs to be monitored. Item Description HBA WWN HBA WWNs to be applied. WWN Name WWN Names to be applied. Edit WWN Monitor Mode wizard Edit WWN Monitor Mode window Use this window to specify WWNs to be monitored or not to be monitored.
Unmonitored WWNs table A table of WWNs that are going to be unmonitored. Item Description Port ID Name of the port. HBA WWN Worldwide name of the host bus adaptor 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.
Monitored WWNs table A table of WWNs that are going to be unmonitored. Item Description Port ID Name of the port. HBA WWN Worldwide name of the host bus adaptor. 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 Enable Monitor table Confirm the information about the WWNs to be monitored. Item Description Port ID Port name to be monitored. HBA WWN Worldwide name of the host bus adapter to be monitored. WWN Name Nickname of WWN to be monitored. The name consists of up to 64 alphanumeric characters and some signs. Status Status of a WWN to be monitored. Normal: WWN connected with a port is the monitoring target object.
Item Description WWN Name Nickname of WWN not to be monitored. The name consists of up to 64 alphanumeric characters and some signs. Status Status of a WWN not to be monitored. Normal: The WWN connected with a port is the monitoring target object. Non-Integrity: The WWN is not monitored for the corresponding port, but monitored for other ports. Delete Unused WWNs window Use this window to name the task to delete unused WWNs. Item Description Task Name Specify the task name.
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.
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 Use this window to confirm the new monitoring information. Selected WWNs table Confirm the list of combinations of ports and WWNs added as monitoring target objects.
Add to Ports wizard 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.
Available Ports table A list of available ports in the storage system. Item Description Port ID Name of the port available in the storage system. Number of Monitored WWNs 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.
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 locate the mouse cursor to each point of the graph, a detailed value is displayed with the tool tip. • When you click the explanatory note on the right of the graph panel, you can display 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.
Available Objects table The columns depend on the object selected. For details, see “Available Objects table”. Add Adds objects to display the graph. 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. OK Displays the graph. Cancel Cancels this operation and closes this window. Help Opens the help topic for this window.
Object and Monitor Data combinations The following table shows the possible Object and Monitor Data combinations that can be selected in the Performance Objects area of the Monitor Performance window. • If Controller is selected on the left side of the Object field, the item on the right side of Monitor Data field is blank.
Item on right side of Object field • Item on left side of Monitor Data field Unit of monitoring data Data Trans. MB/s Response Time ms If Logical Device is selected on the left side of the Object field, the item on the right side of the Object field is blank.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Drive Access Rate Read (Sequential) % Read (Random) Write (Sequential) Write (Random) Business Copy • None % 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.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Drive To Cache (Sequential) Drive To Cache (Random) Drive Usage Rate • None % If LUN is selected on the left side of the Object field, the item on the right side of the Object field is blank.
• 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 Parity Group Parity Group ID ID of the parity group. Only the parity groups assigned to the user are displayed. LUN Port ID Name of the port. Host Group Name Name of the host group. LUN ID of the LUN. Only the LUNsthat correspond to the hostgroups and LDEVs assigned tothe user are displayed. LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV. Only the LDEVs assigned to the user aredisplayed. LDEV Name Name of the LDEV.
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. OK Shows the graph. Cancel Cancels this operation and closes this window. Help Opens the help topic for this window.
Object and Monitor Data combinations The following table shows the possible Object and Monitor Data combinations that can be selected in the Performance Objects area of the Monitor Performance window. • If Controller is selected on the left side of the Object field, the item on the right side of Monitor Data field is blank.
Item on right side of Object field • Item on left side of Monitor Data field Unit of monitoring data Data Trans. MB/s Response Time ms If Logical Device is selected on the left side of the Object field, the item on the right side of the Object field is blank.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Drive Access Rate Read (Sequential) % Read (Random) Write (Sequential) Write (Random) Business Copy* None % *Only information about internal volumes is displayed. Information about external volumes and FICON DM volumes is not displayed. • 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.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) Drive Usage Rate* None % *Only information about internal volumes is displayed. Information about external volumes and FICON DM volumes is not displayed. • If LUN is selected on the left side of the Object field, the item on the right side of the Object field is blank.
Item on left side of Monitor Data field Item on right side of Monitor Data field Unit of monitoring data Back Trans. Total count/sec Cache To Drive Drive To Cache (Sequential) Drive To Cache (Random) • 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.
Monitoring object Item Description Logical Device LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV. LDEV Name Name of the LDEV. LDEV Name is the combination of fixed characters and numbers. Parity Group Parity Group ID ID of the parity group. LUN Port ID Name of the port. Host Group Name Name of the host group. LUN ID of the LUN. LDEV ID ID of the volume, in the following format: LDKC:CU:LDEV. LDEV Name Name of the LDEV.
Item Description Options Click to specify options for how the table displays information. |< Click to view the first page. < Click to view the previous page. Page Page numbers in N/M format, where N indicates the number of the current page and M indicates total number of pages. > Click to view the next page. >| Click to view the last page.
C Performance Control GUI reference This topic provides reference information about the Performance Control GUI. Performance Control window Item Description Monitoring Switch Enable: Performance Monitor is monitoring the storage system Disable: The storage system is not being monitored. Monitoring Term Specify a period in which to gather monitoring data and display in Performance Control main window. A day is set by default.
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 in the Port tab. • WWN Control indicates the system is controlled by the upper limits and threshold specified in 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 the 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 the ports become prioritized ports. • The threshold value for all the ports becomes 0 (zero). • The window will display a hyphen (-) instead of 0 (zero).
Item Description Tip: To return the control status to No Control, specify Prio. for attributes of all the host bus adapters and then click Apply. Control List Allows you to narrow WWNs in the list: • If All is selected, all the WWNs appear in the list. • If Prioritize is selected, only the prioritized WWNs appear in the list. • If Non-Prioritize is selected, only the non-prioritized WWNs appear in the list. Upper-left tree Ports and the host bus adapters connected to these ports in the storage system.
Item Description You can add a host bus adapter that appears below Monitor and is not yet registered on any other PFC group. If you select a host bus adapter below Non-Monitor or a host bus adapter already registered on an PFC group, the Add NNW button is unavailable. Statistic type Allows you to change the type of performance statistics to be displayed in the WWN list. • If IOPS (I/Os per second) is selected, the list displays I/O rates for ports. The I/O rate indicates the number of I/Os per second.
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 the changes displayed in blue text in the window are canceled.
D Cache Residency GUI reference This topic provides reference information about the Cache Residency GUI. Cache Residency window This window provides the Cache Residency information for the connected XP P9500 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. CHA Channel adapter. A device that provides the interface between the array and the external host system.
RAID Manager The CLI configuration and replication tool for the P9000 or XP disk array that system administrators can use to enter RAID Manager commands from open-system hosts to perform Continuous Access, Business Copy, Database Validator, and Data Retention operations, as well as provisioning commands on logical devices. Remote Web Console A browser-based program installed on the SVP that allows you to configure and manage the disk array. RIO Remote I/O. SVP Service processor.
Index A access paths and I/O usage rates, 36 B back-end performance and I/O usage rates, 42 batch file preparing for use with Export Tool, 91 using termination codes in Export Tool, 93 bind mode, 11, 14 and cache size requirements, 69 Business Copy I/O usage rates, 43 C cache extents, 73 hit rates and I/O usage rates, 40 managing, 75 memory and I/O usage rates, 35 placing LDEVs into cache, 79 placing specific data into cache, 77 releasing LDEVs from cache, 80 releasing specific data from cache, 80 rules,
hard disk drive, 42 hard disk drive access, 43 processor blades, 34 throughput, 37 write pending, 35 interoperability Performance Monitor with other software, 17 I/O rate, 48 related documentation, 83 releasing LDEVs from cache, 80 releasing specific data from cache, 80 replace microprogram, 17, 20 resident cache managing, 75 resource availability, 13 L short range, 30 starting monitoring, 28 statistics, 30 setting storing period, 30 storage ranges, 30 viewing, 30 stopping monitoring, 28 storage capacity
