HP StorageWorks Performance Control XP user guide Part number: T1605-96003 Second edition: December 2005
Legal and notice information © Copyright 2005 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 About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . .
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The svpip subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(at CLPR)42 15 Files containing statistics about remote copy operations by Continuous Access XP Journal and Universal Replicator for z/OS (in the whole disk array) 42 16 Files containing statistics about remote copy operations by Continuous Access XP and Universal for z/OS (at journal groups)43 17 Files containing statistics about remote copy operations by Continuous Access XP Journal and Universal Replicator for z/OS (at LU paths)44 18 Files containing statistics about remote copy operations by Continuous
About this guide This guide provides information about the following: • ”Performance Control XP” • ”Optimal performance of high-priority hosts” on page 11 • ”Automatically disable upper limit control” on page 11 • ”Overview of Performance Control XP procedures” on page 11 • ”Notes on using Performance Control XP” on page 16 • ”Performance Control XP restrictions” on page 18 • ”Using Performance Control XP” on page 18 • ”Troubleshooting Auto LUN/Performance Control Base Monitor and Performance Control XP” on
• HP StorageWorks LUN Configuration and Security Manager XP User Guide for the XP128/XP1024 • HP StorageWorks LUN Configuration and Security Manager XP User Guide for the XP10000/XP12000 • HP StorageWorks Auto LUN XP User Guide for the XP128/XP1024 • HP StorageWorks Auto LUN XP User Guide for the XP10000/XP12000 You can find these documents at http://www.hp.com/support/rwc/manuals.
• Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored. Subscription service HP strongly recommends that customers register online using the Subscriber's choice web site: http://www.hp.com/go/e-updates. Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest driver versions, and firmware documentation updates as well as instant access to numerous other product resources.
1 Performance Control XP Use Performance Control XP to ensure that I/O operations for hosts requiring high performance receive higher priority than I/O operations for other hosts. Optimal performance of high-priority hosts In a storage area network (SAN) environment, disk arrays are usually connected to several host servers. Some types of host servers might require high performance, while the performance of other hosts is less critical.
Procedure for one-to-one connections between HBAs and ports Figure 1 shows an example of a network where each host bus adapter is connected to only one port on the disk array. (Henceforth, this network is referred to as network A.) Host bus adapters and disk array ports are connected directly, rather than through hubs and switches. Figure 1 Network A (one-to-one connections between HBAs and ports) In this example, setting up Performance Control XP requires the following major steps: 1.
For detailed information about monitoring traffic, see ”Setting the priority of ports on disk arrays” on page 22 and ”Measuring traffic between host bus adapters and ports for many-to-many connections” on page 22. Figure 3 Traffic at ports on network A 3. Set an upper limit to traffic at non-prioritized ports. To maintain I/O rates at prioritized ports, set upper limit values to the I/O rate for non-prioritized ports.
(wwn01) in the production server is connected to four disk array ports (1A, 1C, 1A, and 2C). The host bus adapters (wwn02 and wwn03) in the development server are connected to the same four ports. Figure 4 Network B (many-to-many connections between HBAs and ports) In this example, setting up Performance Control XP requires the following major steps: 1. Find WWNs of host bus adapters. Before using Performance Control XP, find the Worldwide Name (WWN) of each host bus adapter in the host servers.
NOTE: Performance Control XP cannot monitor and control the performance of hosts that have host bus adapters placed below the Non-Monitor icon. 3. Set the priority of host bus adapters. In the WWN tab of the Performance Control pane, specify the priority of each host bus adapter. 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 5, you must give high priority to wwn01 and low priority to wwn02 and wwn03.
5. Set an upper limit to traffic between ports and the non-prioritized WWN. To maintain sufficient I/O rates at prioritized WWNs, set upper limit values for the I/O rate for non-prioritized WWNs. When you first set an upper limit, HP recommends that the upper limit be approximately 90 percent of peak traffic. In network B, the peak I/O rate is 200 IO/s on the paths between the non-prioritized WWNs (wwn02 and wwn03) and all four ports on the disk array (1A, 1C, 2A, and 2C).
Graph 2 and the line Ave.(1 min) in Graph 3 is around 150 IO/s. The lines Max (1 min.) and Min (1 min.) in Graph 3 might exceed the upper limit. Graph 1: Actual I/O rate (measured every second) Graph 2: I/O rate displayed in Performance Control XP (with Detail option) Graph 3: I/O rate displayed in Performance Control XP (without Detail option) Figure 9 Graphs indicating changes in port traffic • Continuous Access.
Performance Control XP restrictions The following restrictions apply to the Performance Control panes: • You cannot drag and drop objects. You must use the buttons. • After clicking Performance Control to access Performance Control XP or clicking Plan to access AutoLUN Plan, a new browser opens. While working in the new browser, the main Command View XP or XP Remote Web Console window is inactive. You must exit secondary windows to return to the main Command View XP or XP Remote Web Console window.
• Use the WWN tab to set the limit on performance of non-prioritized WWNs and set the threshold on performance of prioritized WWNs.
• If you double-click a port, the tree collapses to display two items: Monitor and Non-Monitor. The table on the right displays a list of host bus adapters that are connected to the specified port and can be monitored by Performance Control XP. • If you double-click Monitor, the tree view and table display a list of host bus adapters that are connected to the specified port and can be monitored by Performance Control XP.
• Threshold: In the Port tab, specifies the threshold for I/O and transfer rates for each prioritized port. Use the IOPS column to specify the threshold for I/O rates. Use the MB/s column to specify the threshold for transfer rates. To specify a threshold, double-click a cell to display the cursor in the cell. • Upper: Specifies the upper limit on I/O and transfer rates for each non-prioritized port or WWN. Use the IOPS column to specify the upper limit for I/O rates.
Setting the priority of ports on disk arrays If a one-to-one connection is established between HBAs and ports, you must measure traffic between high-priority HBAs and prioritized ports and between low-priority HBAs and non-prioritized ports. 1. Start Performance Control XP (”Starting Performance Control XP” on page 18). The Performance Control pane appears. 2. Click Port. 3. Select All from the list at the top right corner of the pane. 4. Right-click a high-priority port, and select Non-Prio.
8. Click Monitor. The table on the right lists HBAs that are displayed below Monitor. 9. Right-click a prioritized WWN, and select Non-Prio. ->> Prioritized. If there is more than one high-priority port, repeat this operation. Prio. is displayed in the Attribute column. 10.Right-click a non-prioritized WWN, and select Prio. ->> Non-Prio. If there is more than one non-prioritized WWN, repeat this operation. Non-Prio. is displayed in the Attribute column. 11.
4. Locate the non-prioritized port or WWN. The Attribute column indicates whether ports or WWNs are prioritized or non-prioritized. If you cannot find non-prioritized ports or WWNs, check the list at the top right corner of the pane. If it displays Prioritize, select All or Non-Prioritize from the list. 5. Do either of the following: • To limit the I/O rate, double-click the desired cell in the IOPS column in Upper, and enter the upper limit in the cell.
The following is the procedure for changing an existing PFC name. For details about assigning PFC names, see ”Measuring traffic between host bus adapters and ports for many-to-many connections” on page 22. 1. Start Performance Control XP (”Starting Performance Control XP” on page 18). The Performance Control pane appears. 2. Click WWN. 3. In the upper-left tree view, click a host bus adapter ( right-click the selection. ) from below the Monitor branch, and 4. Select Change WWN & PFC Name.
4. Select Add New PFC Group. The Add New PFC Group dialog box appears. Figure 14 Add New PFC Group dialog box 5. Enter the name of the PFC group, and click OK. A PFC group is created and a PFC group icon ( is added to the lower-left tree view. 6. Select an HBA ( Click Add WWN. ) ) from the upper-left tree view, and select a PFC group from the lower-left tree view. Repeat this operation until all desired HBAs are added to the PFC group. NOTE: Select a host bus adapter from below the Monitor branch.
NOTE: If you cannot see the IOPS or 100KB/s column, scroll to the left. The column is located at the right side of the table. If you selected a PFC group, take the following steps: a. Right-click the selected PFC group, and select Change Upper Limit. The Change Upper Limit dialog box appears. Figure 15 Change Upper Limit dialog box b. To assign an upper limit to the I/O rate, enter the upper limit value, select IOPS from the list, and click OK.
3. Double-click all Monitor and Non-Monitor entries that appear below the specified ports. 4. If you find HBAs below the Non-Monitor entries, drag them to Monitor. 5. Ensure that the HBA appears below each of the Monitor entries, and click Apply.
2 Performance Control Export Tool This user guide provides additional instructions for using the Export Tool. This user guide makes the following assumptions: • The user has a background in data processing and understands XP disk arrays and their basic functions. • The user is familiar with Command View XP or XP Remote Web Console.
Here is an example of a text file imported into spreadsheet software: Figure 17 Sample text file NOTE: • When you run the Export Tool, text files are usually compressed in a ZIP-format archive file. To be able to open a text file, you must decompress the ZIP file to extract the text files. • Text files are in CSV (comma-separated value) format, in which values are delimited by commas. Many spreadsheet applications can be used to open CSV files.
Table 2 shows the correspondence between the panes of Auto LUN XP and the monitoring data that can be saved by the Export Tool. For details on the ZIP files and CSV files that are saved, see the tables indicated in the See column.
Table 3 Files containing statistics about resource usage and write pending rates (continued) ZIP file CSV file Data saved in the file PhyLDEV_dat.ZIP PHY_Long_LDEV_x-y.csv Usage rates for logical volumes in a parity group in long range NOTE: x-y in the CSV filename is a parity group ID. PHY_Short_LDEV_x-y.csv Usage rates for logical volumes in a parity group in short range NOTE: x-y in the CSV filename is a parity group ID. PhyExG_dat.ZIP PhyExLDEV_dat.ZIP PHY_ExG_Response.
Table 3 Files containing statistics about resource usage and write pending rates (continued) ZIP file CSV file Data saved in the file PhyCSW_dat.ZIP PHY_Long_MPA_CSW.csv • • PHY_Short_MPA_CSW.csv • • PHY_Long_MPA_SMA.csv • • PHY_Short_MPA_SMA.
Table 4 Files containing statistics about parity, external volume, and V-VOL groups ZIP file CSV file Data saved in the file PG_dat.ZIP PG_IOPS.csv The number of read and write operations per second PG_TransRate.csv The size of data transferred per second (unit is KB/sec) PG_Read_IOPS.csv The number of read operations per second PG_Seq_Read_IOPS.csv The number of sequential read operations per second PG_Rnd_Read_IOPS.csv The number of random read operations per second PG_CFW_Read_IOPS.
Table 5 Files containing statistics about logical volumes in parity, external volume, or V-VOL groups ZIP file CSV file Data saved in the file LDEV_IOPS.ZIP LDEV_IOPS_x-y.csv The number of read and write operations per second LDEV_TransRate.ZIP LDEV_TransRate_x-y.csv The size of data transferred per second (unit is KB/sec) LDEV_Read_IOPS.ZIP LDEV_Read_IOPS_x-y.csv The number of read operations per second LDEV_Seq_Read_IOPS.ZIP LDEV_Seq_Read_IOPS_x-y.
Table 5 Files containing statistics about logical volumes in parity, external volume, or V-VOL groups ZIP file CSV file Data saved in the file LDEV_D2CR_Trans.ZIP LDEV_D2CR_Trans_x-y.csv The number of data transfer operations from disk drives (for example, logical volumes) to cache memories in random access mode LDEV_Response.ZIP LDEV_Response_x-y.csv The response time of logical volumes (unit is microseconds1) 1.
Table 8 Files containing statistics about LU paths ZIP file CSV file Data saved in the file LU_dat.ZIP LU_IOPS.csv The number of read and write operations per second LU_TransRate.csv The size of data transferred per second (unit is KB/sec) 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.
Table 10 Files containing statistics about host bus adapters belonging to SPM groups ZIP file CSV file Data saved in the file PPCGWWN_dat.ZIP PPCGWWN_xx_IOPS.csv The I/O rate (that is, the number of read and write operations per second) for HBAs belonging to an SPM group PPCGWWN_xx_KBPS.csv The transfer rate for HBAs belonging to an SPM group (the unit is KB/sec) PPCGWWN_xx_Response.csv The response time of HBAs belonging to an SPM group (unit is microseconds1) PPCGWWN_NotGrouped_IOPS.
Table 11 Files containing statistics about remote copy operations by Continuous Access XP and TrueCopy for z/OS (in the whole disk array) ZIP file CSV file Data saved in the file RemoteCopy_dat.ZIP RemoteCopy.
Table 12 Files containing statistics about remote copy operations by Continuous Access XP and TrueCopy for z/OS (at LU paths) ZIP file CSV file Data saved in the file RCLU_dat.ZIP RCLU_All_RIO.csv Total number of remote I/Os (read and write operations) RCLU_All_Read.csv Total number of remote read I/Os RCLU_All_Write.csv Total number of remote write I/Os RCLU_RIO_Error.csv Number of errors that occur during remote I/O RCLU_Initial_Copy_RIO.
Table 13 Files containing statistics about remote copy operations by Continuous Access XP and TrueCopy for z/OS (at logical volumes controlled by a particular CU) ZIP file CSV file Data saved in the file RCLDEV_All_RIO.ZIP RCLDEV_All_RIO_xx.csv Total number of remote I/Os (read and write operations) RCLDEV_All_Read.ZIP RCLDEV_All_Read_xx.csv Total number of remote read I/Os RCLDEV_All_Write.ZIP RCLDEV_All_Write_xx.csv Total number of remote write I/Os RCLDEV_RIO_Error.ZIP RCLDEV_RIO_Error_xx.
Table 13 Files containing statistics about remote copy operations by Continuous Access XP and TrueCopy for z/OS (at logical volumes controlled by a particular CU) (continued) ZIP file CSV file Data saved in the file RCLDEV_Pair_Synchron ized.ZIP RCLDEV_Pair_Synchronize Percentage of completion of copy operations (that d_xx.csv is, number of synchronized pairs / total number of pairs) RCLDEV_Out_of_Tracks .ZIP RCLDEV_Out_of_Tracks_xx Number of tracks that have not yet been copied by .
1. 1 millisecond is one-thousandth of 1 second Table 16 Files containing statistics about remote copy operations by Continuous Access XP and Universal for z/OS (at journal groups) ZIP file CSV file URJNL_dat.ZIP URJNL_Read_Record.csv Data saved in the file Number of read I/Os per second URJNL_Read_Hit.csv Number of read hit records per second URJNL_Write_Record.csv Number of write I/Os per second URJNL_Write_Hit.csv Number of write hit records per second URJNL_Read_Transfer.
Table 17 Files containing statistics about remote copy operations by Continuous Access XP Journal and Universal Replicator for z/OS (at LU paths) ZIP file CSV file Data saved in the file URLU_dat.ZIP URLU_Read_Record.csv Number of read I/Os per second URLU_Read_Hit.csv Number of read hit records per second URLU_Write_Record.csv Number of write I/Os per second URLU_Write_Hit.csv Number of write hit records per second URLU_Read_Transfer.
• Java™ Runtime Environment (JRE) To be able to use the Export Tool, you must install Java Runtime Environment on your Windows or UNIX computer. If your computer runs Command View XP or XP Remote Web Console, JRE is already installed on your computer and you can install the Export Tool. If your computer does not run Command View XP or XP Remote Web Console but contains an appropriate version of JRE, you can install the Export Tool on your computer.
NOTE: • The export directory contains a couple of files, which includes runUnix.bat. It is recommended that you delete runUnix.bat because this file is no longer needed. • The Export Tool program is a Java class file and is located in the export\lib directory. Installing the Export Tool on a UNIX computer To install the Export Tool on a UNIX computer: 1. Create a directory on your UNIX computer. In later steps, you will install the Export Tool on the new directory. 2.
Here is a sample command file: svpip 158.214.135.
The following is an example of information that the show subcommand outputs: Short Range Long Range Remote Copy From: 2004/10/01 01:00 From: 2004/09/01 00:00 From: 2004/09/30 00:00 - To: 2004/10/01 15:00Interval : 1min To: 2004/10/01 15:00Interval : 15min To: 2004/10/01 15:00 Short Range indicates the storing period and gathering interval of the monitoring data stored in short range. Long Range indicates those of the monitoring data stored in long range.
PhyPG Long subcommand in this example. When you run the Export Tool, it will export the usage statistics about parity groups in the term specified by the longrange subcommand. If you run the Export Tool without specifying the shortrange or longrange subcommand, the monitoring data in the whole storing period (data in the period displayed by the show subcommand) will be exported. For detailed information about the shortrange subcommand, see ”The shortrange subcommand” on page 68.
If the computer that runs the Export Tool communicates directly with the SVP, you usually do not need to change scripts in runWin.bat and runUnix.bat. However, you might need to edit the java command script in your text editor in some occasions, for example: • If the name of your command file is not command.
Running the Export Tool To run the Export Tool and save monitoring data in files, you need to execute your batch file. To execute your batch file, you need to enter the name of the batch file at the command prompt and then press the Enter key (see Figure 22 for reference). If you are using a Windows computer, you can double-click the batch file to execute the batch file. c:\WINDOWS> cd c:\export c:\export> runWin.bat ← Go to the directory containing runWin.bat ← Execute runWin.
Table 19 Errors for which the Export Tool retries processing (continued) Error message ID Cause of error 0002 5510 Disk array is refreshing, or another user is changing configuration. 0002 6502 Now processing. 0002 9000 Another user has lock. 0003 2016 SNMP or SVP has lock. 0003 2033 Server is not ready yet, or internal processing is being executed. 0003 3006 An error occurred. 0405 8003 Disk array status is invalid.
• Whenever the Export Tool runs, it creates a new log file on your computer. Therefore, if you run the Export Tool repeatedly, the size of free space on your computer will be reduced. To secure free space on your computer, you are strongly recommended to delete log files regularly. For information about the directory containing log files, see ”The java command for exporting data In files” on page 76.
Table 22 Subcommand list (continued) Subcommand Function See login Logs the specified user into the SVP. ”The login subcommand” on page 56 show Checks the SVP to find the period of monitoring data stored in the SVP and the data collection interval (called the gathering interval), and then outputs them to the standard output and log file. ”The show subcommand” on page 57 group Specifies the type of data to be exported.
Indicates that a previously used operand can be repeated. For detailed information, see Table 23. Table 23 Syntax descriptions Syntax The syntax indicates that you can write the following script connectΔip-address connect 123.01.22.33 destinationΔ[directory] • • destination destination c:\temp compressΔ[yes|no] • • • compress compress yes compress no answerΔ{yes|no} • • answer yes answer no portsΔ[name][Δ...
Example The following example specifies the IP address of the SVP as 158.214.127.170. svpip 158.214.127.170 The retry subcommand Syntax retryΔ[time=m]Δ[count=n] Description The retry 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.
Operands userid Specifies the user ID for the SVP. If the user ID includes any non-alphanumeric character, the user ID must be enclosed by double quotation marks ("). NOTE: Be sure to specify a user ID that should be used exclusively with the Export Tool. For detailed information, see ”Requirements for using the Export Tool” on page 44. 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 (").
Storing periods output by the show subcommand is the same as the information displayed in the Monitoring Term area of the Auto LUN XP pane (see Figure 26). Figure 26 Information output by the show subcommand The login command must execute before the show subcommand executes. The group subcommand Syntax groupΔ{PhyPGD[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...]| PhyLDEVΔ[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...] | PhyExGΔ[[exg-id]:[exg-id]][Δ...]| PhyExLDEVΔ[[exg-id]:[exg-id]][Δ...
Table 24 shows the monitoring data that can be saved into files by each operand, and the saved ZIP files. For details on the monitoring data saved in these files, see the tables indicated in the See column. Table 24 Operands of the group subcommand and saved monitoring data Operand Pane of Auto LUN XP Monitoring data saved in the file PhyPG Physical tab in the Usage statistics about parity Auto LUN XP pane groups Saved ZIP file See PhyPG_dat.
Table 24 Operands of the group subcommand and saved monitoring data (continued) Operand Pane of Auto LUN XP Monitoring data saved in the file Saved ZIP file See RemoteCopy CA Monitor pane and TCz Monitor pane Statistics about remote copy operations by Continuous Access XP and TrueCopy for z/OS (in the whole disk array) RemoteCopy_dat.ZIP Table 11 RCLU Statistics about remote copy operations by Continuous Access XP and TrueCopy for z/OS (at LU paths) RCLU_dat.ZIP Table 12 RCLDEV RCLDEV_XXXXX.
If an operand is used more than one time in a command file, the last operand takes effect. In the example below, the first group subcommand does not take effect, but the second group subcommand takes effect: group PortWWN CL1-A:CL1-B group PortWWN CL2-A:CL2-B Use an operand starting with Phy (for example, PhyPG or PhyPROC) when you want to export data displayed in the Physical tab in the Auto LUN XP pane.
When you specify variables exg-id, you can narrow the range of external volume groups whose monitoring data are to be exported. exg-id is an ID of an external volume group. The colon (:) indicates a range. For example, E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of the colon. For example, you can specify PhyExG E1-1:E1-5, but you cannot specify PhyExG E1-5:E1-1.
PGΔ[[parity-group-id|V-VOL-group-id|exg-id]: [parity-group-id|V-VOL-group-id|exg-id]][Δ...] Use this operand when you want to export statistics about parity, external volume, or V-VOL groups, which are displayed in the LDEV tab of the Auto LUN XP pane. When statistics are exported to a ZIP file, the file name will be PG_dat.ZIP. For details on the statistics exported by this operand, see Table 4 on page 34.
PortWWNΔ[[port-name]:[port-name]][Δ...] Use this operand when you want to export statistics about host bus adapters (WWNs) connected to ports, which are displayed in the Port-LUN tab of the Auto LUN XP pane. When statistics are exported in a ZIP file, the file name will be PortWWN_dat.ZIP. For details on the statistics exported by this operand, see Table 7 on page 36. When you specify variables port-name, you can narrow the range of ports whose monitoring data are to be exported. port-name is a port name.
If SPM-group-name is not specified, the monitoring data of all the SPM groups will be exported. PPCGWWNΔ[[SPM-group-name]:[SPM-group-name]][Δ...] Use this operand when you want to export statistics about host bus adapters (WWNs) belonging to SPM groups, which are displayed in the WWN tab of the Auto LUN XP pane. When statistics are exported in a ZIP file, the file name will be PPCGWWN_dat.ZIP. For details on the statistics exported by this operand, see Table 10 on page 38.
When you specify variables CU-id, you can narrow the range of CUs that control the logical volumes whose monitoring data are to be exported. CU-id is an ID of a CU. The colon (:) indicates a range. For example, 00:05 indicates CUs from 00 to 05. Ensure that the CU-id value on the left of the colon is smaller than the CU-id value on the right of the colon. For example, you can specify RCLDEV 00:05, but you cannot specify RCLDEV 05:00.
CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify URLU CL1-C.01:CL2-A.01, but you cannot specify URLU CL2-A.01:CL1-C.01. Also, you can specify URLU CL1 C.01:CL1 C.03, but you cannot specify URLU CL1-C.03:CL1-C.01. If port-name.host-group-id is not specified, the monitoring data of all the LU paths will be exported. URLDEV Δ[[CU-id]:[CU-id]][Δ...
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 The shortrange subcommand Syntax shortrangeΔ[[yyyyMMddhhmm][{+|-}hhmm]:[yyyyMMddhhmm][{+|-}hhmm]] Description The shortrange subcommand enables you 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.
-hhmm Subtracts time (hhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example, 200401230000-0130 indicates Jan. 22, 2004, 22:30. Subtracts time from the ending time for collecting monitoring data, if yyyyMMddhhmm is omitted. NOTE: If the last two digits 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.
shortrange 200401010900+0130:200401011700-0130 The Export Tool saves monitoring data within the range of Jan. 1, 10:30-15:30. shortrange 200401010900-0130:200401011700+0130 The Export Tool saves monitoring data within the range of Jan. 1, 7:30-18:30. shortrange 200401010900-0130: The Export Tool saves monitoring data within the range of Jan. 1, 7:30 to Jan. 2, 00:00.
The starting and ending times for collecting monitoring data are displayed in the Monitoring Term area in the Auto LUN XP pane (see Figure 28). Figure 28 The starting time and the ending time for collecting monitoring data yyyyMMddhhmm yyyyMMdd indicates the year, the month, and the day. hhmm indicates the hour and the minute. If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring data is assumed.
longrange +000015: The Export Tool saves monitoring data within the range of Jan. 1, 0:15 to Jan. 2, 00:00. longrange -000015: The Export Tool saves monitoring data within the range of Jan. 1, 23:45 to Jan. 2, 00:00. longrange :+000015 The Export Tool saves monitoring data within the range of Jan. 1, 0:00-00:15. longrange :-000015 The Export Tool saves monitoring data within the range of Jan. 1, 0:00-23:45. longrange +000115:-000115 The Export Tool saves monitoring data within the range of Jan.
The following example saves files in the out directory in the current directory: outpath out The option subcommand Syntax optionΔ[compress|nocompress]Δ[ask|clear|noclear] Description The option 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 Operands The two operands below specify whether to compress CSV files into ZIP files.
The set subcommand Syntax setΔ[switch={m|off}] Description The set subcommand starts or ends monitoring the disk array (that is, starts or ends collecting performance statistics). The set subcommand also specifies the gathering interval (interval of collecting statistics) in short range monitoring. If you want to use the set subcommand, you must use the login subcommand (see ”The login subcommand” on page 56) to log onto the SVP.
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 The help subcommand Syntax help Description The help subcommand displays the online Help for subcommands. If you want to view the online Help, it is recommended that you create a batch file and a command file that are exclusively used for displaying the online Help. For detailed information, see Example below.
• -Dhttp.proxyHost=host-name-of-proxy-host, or -Dhttp.proxyHost=IP-address-of-proxy-host Specifies the host name or the IP address of a proxy host. You must specify this parameter if the computer that runs the Export Tool communicates with the SVP via a proxy host. • -Dhttp.proxyPort=port-number-of-proxy-host Specifies the port number of a proxy host. You must specify this parameter if the computer that runs the Export Tool communicates with the SVP via a proxy host. • -Dmd.
Troubleshooting the Export Tool Table 26 explains possible problems with the Export Tool and probable solutions to the problems. Table 26 Troubleshooting the Export Tool Possible problems Probable causes and recommended action You cannot run the batch file. • • The Export Tool stops and the processing does not continue. The command prompt window was displaying progress of the export processing, but the window stopped displaying progress before the processing stops.
Table 26 Troubleshooting the Export Tool (continued) Possible problems Probable causes and recommended action The monitoring data in the CSV file includes "-1". The value "-1" indicates that Auto LUN XP failed to obtain monitoring data for some reasons. Probable reasons are: • • The Check License row in the log file says UnmarshalException. Auto LUN XP attempted to obtain statistics when an operation for rebooting the disk array is in progress. A heavy workload is imposed on the disk array.
Table 27 Messages to be issued by the Export Tool (continued) Possible problems Probable causes and recommended action Missing output directory No directory is specified for saving files. Please specify the directory for saving files. Missing password The Export Tool cannot find the user ID, which is used to log into the SVP. Specify the password. Missing svpip The svpip subcommand is not used. Use the svpip command. Missing time range Specify the time range.
Table 27 Messages to be issued by the Export Tool (continued) Possible problems Probable causes and recommended action Some file exists in path. What do you do? clear(c)/update(u)/stop(p) You selected “action”. Is it OK? (y/n) Files exist in path. • • • If you want to clear the files, press the c key. If you want to overwrite the files, press the u key. If you want to stop the operation, press the p key. When you press a key, a message appears and asks whether to perform the specified action.
Limitations of Auto LUN XP The Auto LUN XP functions which are limited when you logged in as a storage partition administrator are shown in Table 28. For the pane of Auto LUN XP displayed when you logged in as a storage partition administrator, see Figure 29.
Limitations of the Export Tool The Export Tool functions that are limited when you logged in as a storage partition administrator are as follows: • Only the monitoring data about SLPR allocated to the user ID can be exported into files.
Index A apply subcommand 74 audience, documentation 7 authorized resellers, HP 9 Auto LUN XP 29, 31, 82 B batch files preparing 49 running 51 syntax 54 troubleshooting 78 C command files, preparing 46 commands, Export Tool 53 comma-separated value files 30 comments, inserting 47 Continuous Access XP 29, 39 Continuous Access XP Journal 29 conventions, document 8 CSV files 30 customer support 8 D deleting PFC groups 27 development servers 11 document conventions 8 documentation, related 7 E errors, Export
I S I/O rate 12, 16 installing Export Tool UNIX 46 Windows 45 semicolons 47 servers, production and development 11 set subcommand 75 shortrange subcommand 68 show subcommand 57 SPM group statistics 37 spreadsheets, exporting to 29 starting Performance Control 18 statistics Auto LUN XP 31 exporting 29 external volume 34 host bus adapters (HBAs) 36, 38 logical volumes 35 LU paths 37 parity 34 ports 36 remote copy operations 39 resource usage 31 SPM groups 37 traffic 23 Universal Replicator for z/OS 42 V-VO
HP documentation 8 HP storage 9 HP Subscriber’s choice 9 Windows, installing Export Tool 45 write pending rates 31 WWN tab, Performance Control pane 19 WWNs threshold control 24 upper limit values 23 Z ZIP-format files 30 Performance Control XP user guide 87
88
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Network A (one-to-one connections between HBAs and ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Priority specified in the Performance Control pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic at ports on network A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Auto LUN XP panes and monitoring data that can be saved by the Export Tool . . . . . . . . . . . . . . . . . 31 Files containing statistics about resource usage and write pending rates . . . . . . . . . . . . . . . . . . . . . . .
