HP StorageWorks Performance Control XP user guide Part number: T1605-96007 Fifth edition: September 2007
Legal and notice information © Copyright 2005, 2007 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 Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing a command file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing a batch file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The java command for exporting data In files . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 6 Files with stats. on rem. copy opers. by CA XP and TC for z/OS (at log. vols. contr. by a CU) . . . . . . . 42 Files with statistics about rem. copy opers. by CA XP and TC for z/OS (at CLPR). . . . . . . . . . . . . . . . . 43 Files with stats. about rem. copy opers. by CA XP Journal and UR for z/OS (in the array) . . . . . . . . . . 43 Files with stats. about rem. copy opers. by CA XP and UR for z/OS (at jour. groups) . . . . . . . . . . . . .
About this guide This guide provides information about: • Understanding Performance Control XP • Starting Performance Control XP • Using the Performance Control pane • Managing traffic between HBAs and ports • Grouping host bus adapters • Troubleshooting Auto LUN/Performance Control Base Monitor and Performance Control XP • Using the Performance Export Tool to export monitoring data to files • Troubleshooting the Performance Export Tool • Understanding limitations for storage partition administrators Suppo
You can find these documents at http://www.hp.com/support/rwc/manuals Document conventions and symbols Document conventions Table 1 Convention Element Blue text: Table 1 Cross-reference links and e-mail addresses Blue, underlined text: (http://www.hp.
Subscription service HP recommends that you register your product at the Subscriber’s Choice for Business website: http://www.hp.com/go/e-updates. After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.
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, 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 array. (Henceforth, this network is referred to as network A.) Host bus adapters and 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 arrays” on page 22 and ”Measuring traffic between host bus adapters and ports for many-to-many connections” on page 23. 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 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 array (1A, 1C, 2A, and 2C).
minute), if you set an upper limit of 150 IO/s to port 1A, the highest data point in the line CL1-A in 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.
• 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.
2 Using Performance Control XP Starting Performance Control XP 1. In the Auto LUN pane, click WWN or Port-LUN. 2. Click the PFC button. The Performance Control pane appears. Performance Control pane The Performance Control pane contains two tabs: Port and WWN. • Use the Port tab to set the limit on performance of non-prioritized ports and set the threshold on performance of prioritized ports.
• 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.
Non-Prio. appears in the Attribute column. 6. Click Apply. Settings on the pane are applied to the array. 7. For instructions on measuring traffic (I/O and transfer rates), see the HP StorageWorks Auto LUN XP user guide for the specific array. Measuring traffic between host bus adapters and ports for many-to-many connections If a many-to-many connection is established between host bus adapters (HBAs) and ports, you must measure traffic between each HBA and the port to which the HBA is connected. 1.
Analyzing traffic statistics With one-to-one connections, traffic statistics consist of the number of I/Os made via ports and the amount of data transferred via ports. Analyze traffic statistics to determine upper limit values that should be applied to I/O or transfer rates for non-prioritized ports. With many-to-many connections, traffic statistics consist of the number of I/Os made via ports from HBAs and the amount of data transferred between ports and HBAs.
Setting thresholds If threshold control is used, upper limit control is automatically disabled when traffic between production servers and the array is reduced to a specified level. For details, see ”Automatically disabling upper limit control” on page 11, and ”Procedure for one-to-one connections between HBAs and ports” on page 12 or ”Procedure for many-to-many connections between HBAs and ports” on page 13. 1. Start Performance Control XP (”Starting Performance Control XP” on page 19).
4. Select Change WWN & PFC Name. The Change WWN and PFC Name dialog box appears. Figure 13 Change WWN and PFC Name dialog box 5. Enter a new PFC name (up to eight characters) in the PFC Name box, and click OK. 6. In the Performance Control pane, click Apply. Settings in the pane are applied to the array. Replacing host bus adapters (many-to-many connections only) If a host bus adapter fails, replace the adapter with a new one.
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. You cannot add HBAs from below the Non-Monitor branch to PFC groups. 7. Click Apply.
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. To assign an upper limit to the transfer rate, enter the upper limit value, select 100KB/s from the list, and click OK. 5. In the Performance Control pane, click Apply. Settings are applied to the array. Renaming PFC groups 1.
3 Troubleshooting Auto LUN/Performance Contr. Base Monitor and Performance Contr. XP If the WWN of a host bus adapter is displayed in red in the WWN tree view, the host bus adapter is connected to two or more ports, but Performance Control XP does not control traffic between the HBA and some ports. To control traffic between the HBA and all connected ports, take the following steps: 1. Start Performance Control XP, and ensure that the WWN tab is displayed. 2.
Troubleshooting Auto LUN/Performance Contr. Base Monitor and Performance Contr.
A Performance Control Export Tool This appendix provides additional instructions for using the Performance Control Export Tool. This appendix makes the following assumptions: • You have a background in data processing and understand arrays and their basic functions. • You are familiar with Command View XP or XP Remote Web Console. • You have read and understand the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for the specific array.
Here is an example of a text file imported into spreadsheet software: Figure 17 Sample text file NOTE: • When running the Export Tool, text files are usually compressed in a ZIP-format archive file. 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. You can use many spreadsheet applications to open CSV files. • Do not run multiple instances of the Export Tool simultaneously.
Table 2 Auto LUN XP panes and monitoring data that can be saved by the Export Tool (continued) Pane Monitoring data See LDEV tab in the Auto LUN XP pane Statistics about parity groups, external LU groups, or V-VOL groups Table 4 Statistics about logical volumes in parity groups, in external LU groups, or in V-VOL groups Table 5 Port-LUN tab in the Auto LUN XP pane Statistics about ports Table 6 Statistics about host bus adapters connected to ports Table 7 Statistics about LU paths Table 8 W
Table 3 Files containing statistics about resource usage and write pending rates (continued) ZIP file CSV file Data saved in the file PhyExLDEV_dat.ZIP PHY_ExLDEV_Response_x-y.csv Response time for logical volumes in an external LU group (unit is microsecond1) PHY_ExLDEV_Trans_x-y.csv Amount of data transferred for logical volumes in an LU volume group (unit is KB/sec) PHY_Long_CHP.csv Usage rates for channel processors in long range PHY_Short_CHP.
NOTE: • The letters x-y in the CSV filename indicate a parity group or external LU group. • Statistics in long range and short range are stored for resource usage and write pending rates. 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 Number of read and write operations per second PG_TransRate.csv Size of data transferred per second (unit is KB/sec) PG_Read_IOPS.
Table 5 36 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 Number of read and write operations per second LDEV_TransRate.ZIP LDEV_TransRate_x-y.csv Size of data transferred per second (unit is KB/sec) LDEV_Read_IOPS.ZIP LDEV_Read_IOPS_x-y.csv 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 Number of data transfer operations from disk drives (for example, logical LUs) to cache memories in random access mode LDEV_Response.ZIP LDEV_Response_x-y.csv Response time of logical LUs (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 Number of read and write operations per second LU_TransRate.csv Size of data transferred per second (unit is KB/sec) LU_Seq_Read_IOPS.csv Number of sequential read operations per second LU_Rnd_Read_IOPS.csv Number of random read operations per second LU_Seq_Write_IOPS.csv Number of sequential write operations per second LU_Rnd_Write_IOPS.
1. 1 microsecond is one-millionth of 1 second NOTE: • The letters xx in the CSV filename indicate the name of an SPM group. • If files are exported to a Windows computer, CSV filenames may end with numbers (for example, PPCGWWN_mygroup_IOPS-1.csv and PPCGWWN_MyGroup_IOPS-2.csv).
Table 11 Files with statistics on remote copy opers. by CA XP and TrueCopy for z/OS (in the array) ZIP file CSV file Data saved in the file RemoteCopy_dat.ZIP RemoteCopy.csv The following data in the whole array is saved: • • • • • • • • • • • • • • • • • • • • • • • • • • • 1.
Table 12 Files with statistics on remote copy opers. by CA 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.csv Number of initial copy remote I/Os RCLU_Initial_Copy_Hit.
Table 13 42 Files with stats. on rem. copy opers. by CA XP and TC for z/OS (at log. vols. contr. by a 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 with stats. on rem. copy opers. by CA XP and TC for z/OS (at log. vols. contr. by a CU) 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 .csv the initial copy or resync copy operation 1.
Table 16 Files with stats. about rem. copy opers. by CA XP and UR for z/OS (at jour. groups) (continued) ZIP file CSV file Data saved in the file URJNL_dat.ZIP 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.csv Amount of data read per second (unit is KB/sec) URJNL_Write_Transfer.csv Amount of data written per second (unit is KB/sec) URJNL_Initial_Copy_Hit.
Table 18 CU) Files with stats. about rem. copy ops. by CA XP Jour. and UR for z/OS (at log. vols. contrl. by a ZIP file CSV file Data saved in the file URLDEV_Read_Record.ZIP URLDEV_Read_Record_xx.csv Number of read I/Os per second URLDEV_Read_Hit.ZIP URLDEV_Read_Hit_xx.csv Number of read hit records per second URLDEV_Write_Record.ZIP URLDEV_Write_Record_xx.csv Number of write I/Os per second URLDEV_Write_Hit.ZIP URLDEV_Write_Hit_xx.
If you use the Export Tool only to save monitoring data to files, do not assign any permission to the user ID for use with the Export Tool. If a user ID having permission is used with the Export Tool, the array configuration might be changed in an unfavorable way by an unidentified user.
NOTE: • The export directory contains a couple of files, which include runWin.bat. HP recommends deleting runWin.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. Using the Export Tool To export monitoring data, you must prepare a command file and a batch file. This section explains how to prepare a command file and a batch file, and then explains how to run the Export Tool.
CAUTION: When writing the login subcommand in your command file, you must specify a user ID that should be used exclusively for running the Export Tool. See ”Files to be exported” on page 32 for reference. CAUTION: Secure files containing user IDs and password to prevent the information from being compromised and used for access by unauthorized people.
Specify a term within Short Range From XXX To XXX which is output by the show subcommand. • The longrange subcommand is valid for monitoring data in long range. You can use this subcommand only when you specify the PhyPG, PhyLDEV, PhyProc, or PhyCSW operand with the Long option in the group subcommand. (The items that can be saved by these operands are the monitoring data displayed in the Physical tab of the Auto LUN XP pane with selecting longrange.
Batch file for UNIX computers (runUnix.bat) #! /bin/sh ↵ java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServer.jar" -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain ↵ Figure 19 Scripts in batch files NOTE: The ↵ symbol indicates the end of a command line. 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.
Batch file for UNIX computers (runUnix.bat) #! /bin/sh ↵ java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServer.jar" -Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain ↵ Figure 21 Scripts in batch files (when specifying the IP address of a proxy host) NOTE: The ↵ symbol indicates the end of a command line. For detailed information about syntax of the java command, see ”The java command for exporting data In files” on page 75.
those in Table 19, the Export Tool does not retry the processing. In this case, you must quit the command prompt and run the Export Tool again. However, you can change the maximum number of retries using the retry subcommand. For detailed information, see ”The retry subcommand” on page 56. If the error persists, contact your HP account support representative. Table 19 Errors for which the Export Tool retries processing Error message ID Cause of error 0001 4001 An error occurred.
Table 20 Estimate examples of time required for exporting files (continued) Operand for the group subcommand Estimated time Remarks LDEV 60 minutes Assumes: • • 60 minutes LU The Export Tool should save statistics about 8,192 logical volumes within a 24-hour period. The Export Tool is used eight times. Each time the Export Tool is used, the tool obtains statistics within a 3-hour period. Assumes: • • The Export Tool should save statistics about 12,288 LUs within a 24-hour period.
NOTE: The ↵ symbol indicates the end of a command line. Command reference This section explains details about subcommands you can write in your command file and the java command you should use in your batch file. Table 22 lists the subcommands explained in this section. The java command is explained in ”The java command for exporting data In files” on page 75. Table 22 Subcommand list Subcommand Function See svpip Specifies the IP address of the SVP to be logged into.
• [ ] Indicates one or more operands that can be omitted. If two or more operands are enclosed by square brackets and are delimited by vertical bars (|), you can select one of the operands. For detailed information, see Table 23. • { } Indicates you must select one operand from the operands enclosed by the braces. Two or more operands are enclosed by the braces and are delimited by vertical bars (|). For detailed information, see Table 23. Indicates that a previously used operand can be repeated.
Specifies the SVP’s IP address. host-name Specifies the SVP’s host name. If the host name includes any character that is not alphanumeric or a period, the host name must be enclosed by double quotation marks ("). Example The following example specifies the SVP’s IP address 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.
The login subcommand Syntax loginΔuseridΔpassword Description The login subcommand uses a user ID and password to log the specified user in the SVP. The svpip subcommand must execute before the login subcommand executes. The login subcommand fails if monitoring data does not exist in the SVP. 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 (").
Short Range indicates the storing period and gathering interval of monitoring data stored in short range. Long Range indicates those of monitoring data stored in long range. When running the Export Tool, you can export monitoring data within these periods into files. If you use the shortrange or longrange subcommand, you can also narrow the term of data to be exported (see ”The shortrange subcommand” on page 67 or ”The longrange subcommand” on page 69).
} Description The group subcommand specifies the type of monitoring data you want to export. This command uses an operand (such as PhyPG and PhyLDEV above) to specify the type of monitoring data. Table 24 shows 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 Operand Operands of the group subcommand and saved monitoring data (continued) 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 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 following example, 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 Operands PhyPGr[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...] Use this operand to export statistics about parity group usage rates, which appear in the Physical tab of the Auto LUN XP pane.
PhyExLDEVΔ[[exg-id]:[exg-id]][Δ...] Use this operand to export statistics about logical volumes in external LU groups, which appear in the Physical tab of the Auto LUN XP pane. When statistics are exported to a ZIP file, the file name is PhyExLDEV_dat.ZIP. For details on statistics exported by this operand, see Table 3. When specifying exg-id variable, you can narrow the range of external LU groups whose monitoring data are exported. exg-id is an ID of an external LU group. The colon (:) indicates a range.
Ensure that the parity-group-id, exg-id, or V-VOL-group-id value on the left of the colon is smaller than the parity-group-id, exg-id, or V-VOL-group-id value on the right of the colon. For example, you can specify PG 1-1:1-5, but you cannot specify PG 1-5:1-1. Also, you can specify PG 1-5:2-1, but you cannot specify PG 2-1:1-5. If neither of parity-group-id, exg-id, nor V-VOL-group-id is specified, monitoring data for all parity, external LU, and V-VOL groups is exported.
LUΔ[[port-name.host-group-id]:[port-name.host-group-id]][Δ...] Use this operand to export statistics about LU paths, which appear in the Port-LUN tab of the Auto LUN XP pane. When statistics are exported in a ZIP file, the file name is LU_dat.ZIP. For details about statistics exported by this operand, see Table 8. When specifying the port-name.host-group-id variable, you can narrow the range of LU paths whose monitoring data is exported. port-name is a port name.
If SPM-group-name is not specified, monitoring data for all host bus adapters is exported. RemoteCopy Use this operand to export statistics about remote copy operations, which appear in the CA Monitor pane and the TCz Monitor pane. By using this operand, you can export monitoring data about remote copy operations performed by Continuous Access XP and TrueCopy for z/OS in the whole array. When statistics are exported to a ZIP file, the file name is RemoteCopy_dat.ZIP.
Use this operand to export statistics about remote copy operations, which appear in the CAXJ Monitor pane and the URz Monitor pane. By using this operand, you can export monitoring data about remote copy operations performed by Continuous Access XP Journal and Universal Replicator for z/OS in the whole array. When statistics are exported to a ZIP file, the file name is UniversalReplicator.ZIP. For details about statistics exported by this operand, see Table 15. URJNL Δ[[JNL-group-id]:[JNL-group-id]][Δ...
Example The following example exports statistics about host bus adapters and SPM groups.
The login subcommand must execute before the shortrange subcommand executes. Operands The value on the left of the colon (:) specifies the starting time of the period. The value on the right of the colon specifies the ending time of the period. Specify the term within “Short Range From XXX To XXX” which is output by the show subcommand. If no value is specified on the left of the colon, the starting time for collecting monitoring data is assumed.
Example The following examples assume that: • Starting time for collecting monitoring data is Jan. 1, 2004, 00:00 • Ending time for collecting monitoring data is Jan. 2, 2004, 00:00 shortrange 200401010930:200401011730 The Export Tool saves monitoring data within the range of Jan. 1, 9:30-17:30. shortrange 200401010930: The Export Tool saves monitoring data within the range of Jan. 1, 9:30 to Jan. 2, 00:00. shortrange :200401011730 The Export Tool saves monitoring data within the range of Jan.
The longrange subcommand is valid for monitoring data in long range. Monitoring data in long range is the contents displayed in the Physical tab of the Auto LUN XP pane with selecting longrange as the storing period. Monitoring items whose data can be stored in long range are limited. Table 25 shows monitoring items to which the longrange subcommand can be applied, and also shows operands to export those monitoring items.
NOTE: Ensure that mm is 00, 15, 30, or 45. If you do not specify mm in this way, the value on the left of the colon (:) is rounded down to one of the four values. Also, the value on the right of the colon is rounded up to one of the four values. For example, if you specify 200401010013:200401010048, the specified value is regarded as 200401010015:200401010100. Example The following examples assume: • Starting time for collecting monitoring data is Jan.
The outpath subcommand Syntax outpathΔ[path] Description The outpath subcommand specifies the directory to which monitoring data is exported. Operands path Specifies the directory in which files are saved. If the directory includes any non-alphanumeric character, the directory must be enclosed by double quotation marks ("). To specify a back slash (\) in the character string enclosed by double quotation marks, repeat the back slash twice (\\).
Overwrites existing files and directories. Example The following example saves monitoring data in CSV files, not in ZIP files: option nocompress The apply subcommand Syntax 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. Settings made by the group subcommand are reset when the apply subcommand finishes.
To end monitoring, specify off. If this operand is omitted, the set subcommand does not make settings for starting or ending monitoring. Example The following command file saves port statistics, and ends monitoring ports: svpip 158.214.135.57 login expusr passwd show group Port shortrange 200404010850:200404010910 apply set switch=off The following command file starts monitoring remote copy operations. The sampling time interval is 10 minutes. svpip 158.214.135.
The java command for exporting data In files Syntax javaΔ-classpathΔclass-pathΔproperty-parametersΔsanproject.getmondat. RJMdMain Description This java command starts the Export Tool. To start the Export Tool, you must write this java command in the batch file, and run the batch file. Operands class-path Specifies the path to the Export Tool’s class file. The path must be enclosed in double quotation marks ("). property-parameters You can specify the following parameters. At least you must specify -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 problem Probable cause and recommended action You cannot run the batch file. • • The path to the Java Virtual Machine (java.exe) might not be defined in the PATH environment variable. If this is true, you must add that path to the PATH environment variable.
Table 26 Troubleshooting the Export Tool (continued) Possible problem Probable cause and recommended action 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: • • Auto LUN XP attempted to obtain statistics when an operation for rebooting the array is in progress. A heavy workload is imposed on the array.
Table 27 Messages to be issued by the Export Tool (continued) Possible problems Probable causes and recommended action Missing command file The command file is not specified. Specify the name of the command file correctly. Missing group name No operand is specified in the group subcommand. Specify operands for the subcommand. Missing host name No host name is specified. Please specify a host name. Missing output directory No directory is specified for saving files.
Table 27 Messages to be issued by the Export Tool (continued) Possible problems Probable causes and recommended action Unsupported option: option The specified option is not supported. Correct the specified option. 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. • • • To clear the files, press the c key. To overwrite the files, press the u key. To stop the operation, press the p key.
Performance Control Export Tool
B Limitations for storage partition administrators If the user type of your user ID is storage partition administrator, you can use only Auto LUN XP and the Export Tool from the Auto LUN XP programs. In this case, you cannot use Auto LUN XP or Performance Control XP. Also, when logging in as a storage partition administrator, the available functions of Auto LUN XP and the Export Tool are limited. This appendix explains these limitations of Auto LUN XP and the Export Tool.
Figure 29 An example of a text file Limitations of the Export Tool The following Export Tool functions are limited when logging in as a storage partition administrator: • Only monitoring data about the SLPR allocated to the user ID can be exported into files.
Index A apply subcommand 73 audience, documentation 7 Auto LUN XP 31, 32, 81 B batch files preparing 49 running 51 syntax 54 troubleshooting 76 C command files, preparing 47 commands, Export Tool 54 comma-separated value files 32 comments, inserting 47 Continuous Access XP 31, 40 Continuous Access XP Journal 31 conventions document 8 text symbols 8 CSV files 32 customer support 8 D deleting PFC groups 28 development servers 11 document conventions 8 feedback 9 prerequisites 7 related documentation 7 E e
HP storage website 9 Subscriber’s Choice for Business website 9 technical support 8 prerequisites 7 prioritized port 12 prioritized WWN 15 production servers 11 I R I/O rate 12, 16 installing Export Tool UNIX 46 Windows 46 related documentation 7 remote copy operations statistics 40 requirements, Export Tool 45 resource usage statistics 33 restrictions 17 retry subcommand 56 J java command for exporting data in files 75 L limitations 81 logical volumes, statistics 36 login subcommand 57 longrange sub
storage partition administrators 81, 82 storage platforms, supported 7 Subscriber’s Choice for Business, HP 9 supported storage platforms and firmware 7 svpip subcommand 55 symbols in text 8 syntax, command 54 system requirements, Export Tool 45 T technical support, HP 8 termination codes, Export Tool 53 text files, exporting to 31 text symbols 8 threshold control 11, 25 time required for exporting files 52 traffic management 22 traffic statistics 24 transfer rate 12, 16 troubleshooting Export Tool 76 Perf
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 . . . . . . . . . . . . . . . . . 32 Files containing statistics about resource usage and write pending rates . . . . . . . . . . . . . . . . . . . . . . .
