Details
Below are example performance export command.txt scripts to use as a template for performance data collection. These examples are set up in an optimal way to temporarily reduce the length of time it takes to collect data by missing out the LU (LUN path) metrics. If at all possible, leave LUN metrics uncommented for the 5000 and G1500/1000 to ensure comprehensive analysis. You should also check these tips to ensure successful performance data collection:
NOTE: You can also comment out replication outputs if not using any replication. RemoteCopy, RCLDEV, UniversalReplicator, URJNL, URLDEV.
- Select your storage model example below and copy and paste over the old command.txt scripts using a text editor such as Notepad.
- Then edit and change the ip address and the login userid & password to match your requirements.
- Note in the case of using VSP E & N Series and G/F130 thru G/F900 template you must also change the "dkcsn" to match your Storage Serial Number.
- Check performance monitor options are enabled and have the interval set to 1 minute.
- Check performance monitor options have the active CU (Control Units) for DP volumes selected for monitoring.
- There is a limitation to the number of selectable CU dependent on the storage model; either 32 or 64 can be selected for 1-minute intervals; over this number can only report at 5-minute intervals. Therefore, only select active CU as 1-minute intervals is the most preferred and accurate data.
- Use a unique and exclusive userid for the export collection.
- Ensure you use the "option compress" in the command.txt scripts as it is essential for our analysis tools to work correctly.
- Once you have completed running the export collection, zip up the output directory in a format compatible with our automated tools:
- Only include one export per zip archive.
- Ensure the word "out" or "export" is in the archive filename and try to be descriptive in the naming, e.g. PrimaryExport_Sat25thJuly.zip.
- You may also reduce the data to the last 12 or 8 hours or a specific timeframe to speed up collection. However, please ensure you add a few hours on each side of your performance issue to account for clock offsets and comparison of normal workloads.
- Longrange data is not required and can be commented out.
VSP 5000 Series Template
; Notes: ; Ensure all active CU's have been selected for monitoring. ; If possible ensure sampling interval is 1-minute. ; Recommend temporarily commenting out the group *LU below to speed up data collection. ; Output Zip filenames must include "export" or "out" for AutoPAR compatibility. ; Only include one export per zip file. ; Filter log file for "gathering" to see progress of operation. ; comment out longrange svpip x.x.x.x ; Always try to use a unique userid to avoid collection problems: login userid "password" show group PhyPG group PhyLDEV group PhyProc group PhyProcDetail group PhyExG group PhyExLDEV group PhyMPU group PG ;group LDEV group Port group MFPort group PortWWN group LU group PPCGWWN group RemoteCopy ;group RCLU group RCLDEV group UniversalReplicator group URJNL ;group URLU group URLDEV group LDEVEachOfCU ; If required shorten the range to be the last -1200: or -0800: hours: shortrange -2400: ;longrange -030000: outpath outR900 option compress apply |
VSP E & N Series and G/F130 thru G/F900 Template
; Notes: ; Ensure all active CU's have been selected for monitoring. ; If possible ensure sampling interval is 1-minute. ; Recommend commenting out the group *LU below to speed up data collection. ; Output Zip filenames must include "export" or "out" for AutoPAR compatibility. ; Only include one export per zip file. ; Filter log file for "gathering" to see progress of operation. ip x.x.x.x dkcsn 999999 ; Always try to use a unique userid to avoid collection problems: login user "password" show group PhyPG group PhyLDEV group PhyProc group PhyExG group PhyExLDEV group PhyMPU group PG ;group LDEV group LDEVEachOfCU group Port group PortWWN ;group LU group PPCGWWN group RemoteCopy ;group RCLU group RCLDEV group UniversalReplicator group URJNL ;group URLU group URLDEV ; If required shorten the range to be the last -1200: or -0800: hours: range -2400: outpath outHM option compress apply |
VSP G1500/1000 Template
; Notes: ; Ensure all active CU's have been selected for monitoring. ; If possible ensure sampling interval is 1-minute. ; Recommend temporarily commenting out the group *LU below to speed up data collection. ; Output Zip filenames must include "export" or "out" for AutoPAR compatibility. ; Only include one export per zip file. ; Filter log file for "gathering" to see progress of operation. ; comment out longrange svpip xxx.xxx.xxx.xx ; Always try to use a unique userid to avoid collection problems: login userid "password" show group PhyPG group PhyLDEV group PhyProc group PhyExG group PhyExLDEV group PhyCMPK group PhyMPPK group PG ;group LDEV group LDEVEachOfCU group Port group MFPort group PortWWN group LU group PPCGWWN group RemoteCopy ;group RCLU group RCLDEV group UniversalReplicator group URJNL ;group URLU group URLDEV ; If required shorten the range to be the last -1200: or -0800: hours: shortrange -2400: ;longrange -030000: outpath outR800 option compress apply |
Additional Notes
Tags: Performance,Data Collection,Export Tool,export,template,command.txt
PageID: 105357
- Keywords
- https://knowledge.hitachivantara.com/Support_Information/Data_Collection/Storage/Optimal_Performance_Export_CommandTxt_Script_Templates
- Solution ID
- 242403060105357
- Last Modified Date
- 09/30/2024 08:52:33 PM
- Attributes
-
Page Privacy and Permission Assignment
- Page Privacy: Private
- Page Level Permissions: Anonymous; Employee; Service Partner; Customer; Knowledge Author; Knowledge Editor; IT; eServices; Knowledge Draft
- Article: howto
- Pagetype: knowledgearticle
- Taxonomy
-
- Collections
-
-
Customer
-
Employee
-
Support Center
-
Guest
-
Service Partner
- Views
- 0