HP StorageWorks XP Performance Control user guide HP XP12000 Disk Array HP XP10000 Disk Array HP 200 Storage Virtualization System This guide explains how to use HP StorageWorks XP Performance Control software to ensure that I/O operations for high-performance hosts are processed with high priority by HP StorageWorks XP12000/XP10000 disk arrays and the HP 200 Storage Virtualization System.
Legal and notice information © Copyright 2005, 2009 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 XP Performance Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Optimal performance of high-priority hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Automatically disabling upper limit control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview of XP Performance Control procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 statistics on remote copy ops. by Cnt Ac and TC for z/OS (at logical vols. by CU) . . . . . . . . 42 Files with statistics on remote copy operations by Cnt Ac and TC for z/OS (at CLPR) . . . . . . . . . . . . . . 43 Files with statistics on remote copy operations by Cnt Ac-J and UR for z/OS (in the array) . . . . . . . . . . 43 Files with statistics on remote copy ops. by Cnt Ac and UR for z/OS (at journal groups) . . . . . . . . . . .
1 XP Performance Control Use XP Performance Control to ensure that I/O operations for hosts requiring high performance receive higher priority than I/O operations for other hosts. NOTE: TThe functions described in this manual may be limited, depending on your assigned level of user access. Some users will have read-only access while others will have limited or full array access.
Port tab of the XP Performance Control pane. For many-to-many connections between HBAs and ports, use the WWN tab of the XP Performance Control pane. 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.
administrator, you might want to maintain the I/O rate for prioritized ports 1A and 1C at 400 IO/s. To do this, set an upper limit to the I/O rate for port 2A. For detailed information about monitoring traffic, see ”Setting the priority of ports on arrays” on page 18 and ”Measuring traffic between host bus adapters and ports for many-to-many connections” on page 19. Figure 3 Traffic at ports on network A 3. Set an upper limit to traffic at 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 XP Performance Control requires the following major steps: 1. Find WWNs of host bus adapters. Before using XP Performance Control, find the Worldwide Name (WWN) of each host bus adapter in the host servers.
NOTE: XP Performance Control 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 XP 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 XP Performance Control to access XP Performance Control or clicking Plan to access Auto LUN Plan, a new browser opens. While working in the new browser, the main XP Command View Advanced Edition Device Manager or Remote Web Console window is inactive. You must exit secondary windows to return to the main XP Command View Advanced Edition Device Manager or Remote Web Console window.
2 Using XP Performance Control Starting XP Performance Control 1. In the Performance Control pane, click WWN or Port-LUN. 2. Click the PFC button. The XP Performance Control pane appears. XP Performance Control pane The XP 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 XP Performance Control. • 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 XP Performance Control.
• 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.
5. Right-click a low-priority port, and select Prio. ->> Non-Prio. If there is more than one low-priority port, repeat this operation. 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 XP Auto LUN user guide for the specific array.
13. For instructions on measuring traffic (for example, I/O and transfer rates), see the HP StorageWorks XP Auto LUN user guide for the specific array. 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.
6. Click Apply. The settings in the pane are applied to the array. The upper limit value you entered turns black. 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.
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 XP 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 ( ) from the upper-left tree view, and select a PFC group from the lower-left tree view. Click Add WWN. 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 XP Performance Control pane, click Apply. Settings are applied to the array. Renaming PFC groups 1.
3 Troubleshooting XP Auto LUN/Performance Base Monitor and XP Performance Control 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 XP Performance Control 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 XP Performance Control, and ensure that the WWN tab is displayed. 2.
Troubleshooting XP Auto LUN/Performance Base Monitor and XP Performance Control
4 Support and other resources Supported storage platforms and firmware In this guide, the term array refers to the following storage platforms: • HP StorageWorks XP12000 Disk Array • HP StorageWorks XP10000 Disk Array • HP StorageWorks 200 Storage Virtualization System Prerequisites Prerequisites for using this product include: • Installing the HP StorageWorks disk array(s) • Installing the license key for this product Related documentation The following documents provide related information: • HP Stora
IMPORTANT: NOTE: TIP: Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts.
• http://www.hp.com/go/storage • http://www.hp.com/support/manuals • http://www.hp.com/support/rwc/manuals • http://www.hp.com/storage/spock Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.
Support and other resources
A XP Performance Control Export Tool This appendix provides additional instructions for using the XP 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 XP Command View Advanced Edition or Remote Web Console.
Here is an example of a text file imported into spreadsheet software: Transfer rates for LUs (Filename: LU_IOPS.csv) Indicates that the subsystem serial number is 28528. The word in parentheses is a code that indicates the subsystem type. Indicates that the data was obtained from 10:48 to 10:52 on Nov. 25, 2004. Sampling rate: 1 indicates that monitoring was performed every minute (at a one-minute interval). Indicates monitoring data.
Table 2 XP Auto LUN panes and monitoring data that can be saved by the Export Tool (continued) Pane Monitoring data See LDEV tab in the XP Auto LUN 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 XP Auto LUN 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 on resource usage and write pending rates (continued) ZIP file CSV file PhyExLDEV_dat.ZIP PHY_ExLDEV_Response_x-y.csv PhyProc_dat.ZIP PhyCSW_dat.ZIP Data saved in the file Average response time time for logical volumes in an external LU group (in microseconds1) PHY_ExLDEV_Trans_x-y.csv Amount of data transferred for logical volumes in an LU volume group (in 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 on 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 on 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 on 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 Average response time of logical LUs (unit is microseconds1) 1.
Table 8 Files containing statistics on 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.
Table 10 Files containing statistics on host bus adapters belonging to PFC groups ZIP file CSV file Data saved in the file PPCGWWN_dat.ZIP PPCGWWN_xx_IOPS.csv I/O rate (that is, number of read and write operations per second) for HBAs belonging to PFC group PPCGWWN_xx_KBPS.csv Transfer rate for HBAs belonging to an PFC group (unit is KB/sec) PPCGWWN_xx_Response.csv Average response time of HBAs belonging to a PFC group (unit is microseconds1) PPCGWWN_NotGrouped_IOPS.
Table 11 Files with statistics on remote copy ops. by Cnt Ac 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 ops. by Cnt Ac 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 statistics on remote copy ops. by Cnt Ac and TC for z/OS (at logical vols. by 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 statistics on remote copy ops. by Cnt Ac and TC for z/OS (at logical vols. by 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 statistics on remote copy ops. by Cnt Ac and UR for z/OS (at journal groups) 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 17 Files with statistics on remote copy ops. by Cnt Ac-J and UR 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.csv Amount of data read per second (unit is KB/sec) URLU_Write_Transfer.
• Java™ Runtime Environment (JRE) To be able to use the Export Tool, you XP must install Java Runtime Environment on your Windows or UNIX computer. If your computer runs Command View Advanced Edition or Remote Web Console software, JRE is already installed on your computer and you can install the Export Tool. If your computer does not run XP Command View Advanced Edition or Remote Web Console software but contains an appropriate version of JRE, you can install the Export Tool on your computer.
• 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 1. Create a directory on your UNIX computer. In later steps, you will install the Export Tool on the new directory. 2. Insert the Program Products CD in the CD-ROM drive. 3. Do either of the following: • If you are using Solaris, locate the archive file export.tar in the directory /export_tool/solaris in your CD-ROM disc, and copy export.
Subcommands in this command file are explained as follows: • svpip 158.214.135.57 Specifies that you are logging into the SVP whose IP address is 158.214.135.57. You must log into the SVP when using the Export Tool. The svpip subcommand specifies the SVP’s IP address. You must include the svpip subcommand in your command file. For detailed information, refer to ”The svpip subcommand” on page 56. • login expusr passwd Specifies that you use the user ID expusr and the password passwd to log into the SVP.
For detailed information, see ”The group subcommand” on page 58. • shortrange 200410010850:200410010910, and longrange 200409301430:200410011430, and remotecopyrange 200409301430:200410011430 The shortrange and longrange subcommands specify the monitoring data term to be exported. Use these subcommands to narrow the export-target term within the stored data. You can specify both the shortrange and longrange subcommands at the same time.
The installation directory for the Export Tool (that is, the export directory) contains two batch files: runWin.bat and runUnix.bat. If your computer runs Windows, use runWin.bat. If your computer runs UNIX, use runUnix.bat. Figure 3 illustrates scripts in runWin.bat and runUnix.bat. These batch files include a command line that executes a java command. When executing your batch file, the java command executes subcommands specified in your command file, and saves monitoring data in files.
Batch file for Windows computers (runWin.bat) java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerEx.jar" -Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Xmx268435456 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain pause Batch file for UNIX computers (runUnix.bat) #! /bin/sh java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServerEx.jar" -Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Xmx268435456 -Dmd.command=command.txt -Dmd.logpath=log sanproject.
For a complete list of files to be saved by the Export Tool, see ”Files to be exported” on page 32. Notes • When an internal error shown in Table 19 occurs during export processing, the exclamation mark (!) appears and retries export processing. By default, the Export Tool can retry processing up to three times. If export processing does not finish after three retries or if an internal error occurs other than those in Table 19, the Export Tool does not retry the processing.
Table 20 Estimate examples of time required for exporting files (continued) Operand for the group subcommand Estimated time Remarks PPCG 5 minutes Assumes: • • • LDEV 60 minutes Assumes: • • 60 minutes LU There are eight PFC groups, and eight WWNs are registered on each PFC group. There is a WWN that is not registered on any PFC group. The Export Tool should save statistics about PFC groups and WWNs described above within a 24-hour period.
A reference to a termination code is used in the following example of a Windows batch file. If this batch file executes and the Export Tool returns the termination code 1 or 3, the command prompt displays a message that indicates the set subcommand fails. java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServerEx.jar" -Xmx268435456 -Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.
• Conventions used in this section This section uses the following symbols and typefaces to explain syntax: • Indicates a space. • bold Indicates characters you must type as they are. • italics Indicates a type of operand. You do not need to type characters in italics as they are. • [ ] 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.
The svpip subcommand Syntax svpip{ip-address|host-name} Description The svpip subcommand specifies the SVP’s IP address or host name. Operands ip-address 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.
Example In the following command file, the interval between retries is five minutes and the maximum number of retries is 10. svpip 158.214.135.57 retry time=5 count=10 login expusr passwd show group Port shortrange 200404010850:200404010910 outpath out option compress apply The login subcommand Syntax loginuseridpassword 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.
• Period during which monitoring data was collected onto the SVP (storing period). • Interval at which the monitoring data was collected (gathering interval). XP Auto LUN collects statistics by the type of storing period: in short range and in long range. In short-range monitoring, monitoring data between 1 and 15 days is stored in the SVP. In long-range monitoring, monitoring data up to three months is stored in the SVP.
PortWWN[[port-name]:[port-name]][...]| LU[[port-name.host-group-id]:[port-name.host-group-id]][...]| PPCG[[PFC-group-name]:[PFC-group-name]][...]| PPCGWWN[[PFC-group-name]:[PFC-group-name]][...]| RemoteCopy | RCLU [port-name.host-group-id]:[port-name.host-group-id]][...]| RCLDEV [[CU-id]:[CU-id]][...]| RCCLPR | UniversalReplicator| URJNL [[JNL-group-id]:[JNL-group-id]][...]| URLU [port-name.host-group-id]:[port-name.host-group-id]][...]| URLDEV [[CU-id]:[CU-id]][...
Table 24 Operands of the group subcommand and saved monitoring data (continued) Operand XP Auto LUN Pane Monitoring data saved in the file Saved ZIP file See PPCG WWN tab in the XP Auto LUN pane Statistics about PFC groups PPCG_dat.ZIP Table 9 Statistics about host bus adapters belonging to PFC groups PPCGWWN_dat.
You can use the group subcommand more than one time in a command file. For example, you can write the following script: group PortWWN CL1-A:CL1-B group PPCG pfcg01:pfcg02 group RemoteCopy If an operand is used more than one time in a command file, the last operand takes effect.
When specifying the 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. For example, E1-1:E1-5 indicates external LU 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.
Use this operand to export statistics about parity, external LU, or V-VOL groups, which appear in the LDEV tab of the XP Auto LUN pane. When statistics are exported to a ZIP file, the file name is PG_dat.ZIP. For details about statistics exported by this operand, see Table 4. When specifying the parity-group-id, exg-id, or V-VOL-group-id variables, you can narrow the range of parity, external LU, or V-VOL groups whose monitoring data is exported. parity-group-id is a parity group ID.
Ensure that the port-name value on the left of the colon is smaller than the port-name value on the right of the colon. Note that the smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which value is smaller than which value: CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify PortWWN CL1-C:CL2-A, but you cannot specify PortWWN CL2-A:CL1-C.
non-alphanumeric character, the name must be enclosed by double quotation marks ("). The colon (:) indicates a range. For example, Grp01:Grp03 indicates a range of PFC groups from Grp01 to Grp03. Ensure that the PFC-group-name value on the left of the colon is smaller than the PFC-group-name value on the right of the colon. Note that numerals are smaller than letters and lowercase letters are smaller than uppercase letters.
RCCLPR Use this operand to export statistics about remote copy operations, which appear in the XP Continuous Access pane and the TCz Monitor pane. By using this operand, you can export monitoring data about remote copy operations performed by XP Continuous Access and TrueCopy for z/OS at each CLPR. When statistics are exported to a ZIP file, the file name is RCCLPR_dat.ZIP. For details about statistics exported by this operand, see Table 14.
about remote copy operations performed by XP Continuous Access Journal and Universal Replicator for z/OS at logical volumes controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files with names beginning with URLDEV_ are output. For details about statistics exported by this operand, see Table 18. When specifying the CU-id variable, you can narrow the range of CUs that control the logical volumes whose monitoring data is exported. CU-id is an ID of a CU.
Description The shortrange subcommand specifies the term of monitoring data exported into files. Use this subcommand to narrow the export-target term within the stored data. The shortrange subcommand is valid for monitoring data in short range.
NOTE: If the last two digits of the time on the left or right of the colon (:) are not a multiple of the sampling interval, the time automatically changes so the last two digits are a multiple of the sampling interval. If this change occurs to the time on the left of the colon, the time is smaller than the original time. If this change occurs to the time on the right of the colon, the time is larger than the original time.
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 appear in the Monitoring Term area in the XP Auto LUN pane (see Figure 12). Figure 12 Starting and ending time for collecting monitoring data yyyyMMddhhmm yyyyMMdd indicates the year, month, and day. hhmm indicates the hour and minute. If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring data is assumed.
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. 1, 1:15-22:45.
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 following operands specify whether to compress CSV files into ZIP files. If none of these operands is specified, compress is assumed: compress Compresses data in ZIP files.
Description The set subcommand starts or ends monitoring the 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. To use the set subcommand, you must use the login subcommand (see ”The login subcommand” on page 57) to log onto the SVP. Ensure that the set subcommand executes immediately before the Export Tool finishes.
The help subcommand Syntax help Description The help subcommand displays the online Help for subcommands. To view the online Help, HP recommends creating a batch file and command file that are exclusively used for displaying online Help. For detailed information, see the following example. Example In this example, a command file (cmdHelp.txt) and batch file (runHelp.bat) are created in the C:\export directory in a Windows computer: • Command file (c:\export\cmdHelp.
• -Xmxmemory-size(bytes) Specifies the size of memory to be used by JRE when the Export Tool is being executed. You must specify this parameter. The memory size must be 268435456, as shown in the Example later in this section. If an installed memory size is smaller than the recommended memory size of Storage Navigator PC, you must install more memory, before executing the Export Tool.
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 XP Auto LUN failed to obtain monitoring data for some reasons. Probable reasons are: • • XP Auto LUN 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.
B Limitations for storage partition administrators If the user type of your user ID is storage partition administrator, you can use only XP Auto LUN and the Export Tool from the XP Auto LUN programs. In this case, you cannot use XP Auto LUN or XP Performance Control. Also, when logging in as a storage partition administrator, the available functions of XP Auto LUN and the Export Tool are limited. This appendix explains these limitations of XP Auto LUN and the Export Tool.
Figure 13 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 B batch files preparing 49 running 51 syntax 54 troubleshooting 77 C command files, preparing 47 commands, Export Tool 54 comma-separated value files 32 comments, inserting 47 conventions document 27 text symbols 27 CSV files 32 customer support 28 D deleting PFC groups 24 development servers 7 document conventions 27 feedback 29 prerequisites 27 related documentation 27 E errors, Export Tool 52, 77 Export Tool about 31 apply subcommand 73 batch files 49 command files, prepar
I I/O rate 8, 12 installing Export Tool UNIX 47 Windows 46 J java command for exporting data in files 75 L limitations 81 logical volumes, statistics 36 login subcommand 57 longrange subcommand 70 LU path statistics 38 M monitoring data.
XP Performance Control 25 TrueCopy for z/OS 31, 40 U Universal Replicator for z/OS 31, 43 UNIX, installing Export Tool 47 upper limit control 7 user IDs creating 46 limitations 81, 82 V V-VOL groups statistics 35 W websites HP documentation 29 HP SPOCK 29 HP storage 29 HP Subscriber’s Choice for Business 28 Windows, installing Export Tool 46 write pending rates 33 WWN tab, Performance Control pane 16 WWNs threshold control 21 upper limit values 20 X XP Auto LUN 31, 32, 81 XP Continuous Access 31, 40 XP
