DF Performance Data Procedures Mike Le Voi Technical Specialist,
APAC Global Support Centre Hitachi Data Systems 15th January,
2010The DF subsystem family includes 9200, 9500V, AMS and WMS. DF
subsystems support Open Systems applications. The latest version of
this document is available on TUF:
https://tuf.hds.com/gsc/bin/view/Main/DFPerformanceData Always
refer to the TUF link above for complete, up to date instructions.
Introduction When performance problems are reported to GSC it is
important that as much data as possible is collected. We need the
PFM statistics which are generated by DAMP, Storage Navigator
Modular (SNM) or Storage Navigator Modular 2 (HSNM2). DAMP and SNM
can also generate 9500V PFMD statistics, however these stats are
not useful for analysing performance as only LDEV information is
collected. You can collect the PFM stats using the CLI or the GUI.
Either way, we suggest that you login to the array first. If you
attempt to collect stats and someone else logs in to the array, the
data collection for that interval is aborted, in our experience.
For the AMS2000 series, you must use Account Authentication to
login to the array. Here is an example of how to collect stats via
the CLI:aulogin unit BNE9570V auperform -unit BNE9570V -auto 1
-pfmstatis -count 60
-auto 1 -count
means collect stats at 1 minute intervals means collect 60
PFMnnnn.TXT files
Thus, if you issue these commands when performance problems
strike, we will have an hours detailed statistics to look at. Note
that if you use the command below:auperform -unit BNE9570V -auto 1
-count 60
you will only get PFMD stats. This is not enough data to analyse
any performance problem. DAMP, SNM or HSNM2 will generate files
called PFMnnnnn.txt where nnnnn is a number from 00000 to 99999.
For 9500V, the text files written contain a measurement for every
possible raid group and LDEV, whether they exist or not Recommended
Usage Here are the steps you should follow. Note that you should
always provide the configuration output and a Simple Trace as this
allows us to tie the LDEV performance back to the appropriate
servers Host Storage Domains.
GSC highly recommends the use of the CLI to get these statistics
. With a single BAT file you can automate data collection. Using
the GUI to do this is very cumbersome indeed. Here is some
SNM/HSNM2 CLI to get the data. First, make sure that data
collection is enabled. You only need to do this once, of course.
Once enabled, you should leave this setting enabled. All
Modelsaupfmstatiscfg -unit MyDfName set -port start -rglu start
-cache start -processor start -drive start -driveopr start -backend
start
Now collect the configuration files and PFM data. We recommend
using HSNM2 CLI as it is backward compatible and supports all array
types. 9500V DAMP or SNM CLI or HSNM2 CLIaulogin unit BNE9570V
ausyspout -unit BNE9570V -file ausyspout.txt auconfigout -unit
BNE9570V -file auconfigout.txt auhgout -unit BNE9570V -file
auhgout.txt aumluref -unit BNE9570V > aumluref.txt auperform
-unit BNE9570V -auto 1 -pfmstatis -count 60 aulogout unit
BNE9570V
AMS200/500/1000//WMS100 SNM or HSNM2 CLIaulogin unit AMS500
auconstitute -unit AMS500 -export -config AMSconfigout.txt
auconstitute -unit AMS500 -export -sysp AMSsyspout.txt auconstitute
-unit AMS500 -export -hg AMShgout.txt auconstitute -unit AMS500
-export -parts AMSpartsout.txt auconstitute -unit AMS500 -export
-bootopt AMSbootoptout.txt aumluref -unit AMS500 > aumluref.txt
auperform -unit AMS500 -auto 1 -pfmstatis -count 60 aulogout unit
AMS500
AMS2100/2300/2500 HSNM2 CLIauaccountenv -set -uid mlevoi
auconstitute -unit AMS2100 -export -config AMSconfigout.txt
auconstitute -unit AMS2100 -export -sysp AMSsyspout.txt
auconstitute -unit AMS2100 -export -port AMShgout.txt auconstitute
-unit AMS2100 -export -parts AMSpartsout.txt auconstitute -unit
AMS2100 -export -bootopt AMSbootoptout.txt aumluref -unit AMS2100
> aumluref.txt auperform -unit AMS2100 -auto 1 -pfmstatis -count
60 auaccountenv -rm
Obviously, change BNE9570V, AMS500 or AMS2100 to the name of
your storage array. Change the userid for Account Authentication as
well. NB. We have a program which will analyse this data. This
program requires that the config files are saved as .TXT files.
You will find all the above commands in BAT files distributed
with this document. Rename the *.BAT.txt files to *.BAT before use.
Edit the BAT files before use. Refer to the Appendix to see how to
specify these commands via the GUI (not recommended). In
particular, the GUI has no way of outputting the LUSE
configuration. So, our analysis will be less detailed if this
information is missing. Zip up all the files and upload them to
TUF. Finally, collect a Simple Trace via the 9500V/AMS/WMS Web GUI
and upload it to TUF as well. Instructions on how to collect a
Simple Trace are available here:
https://tuf.hds.com/gsc/bin/view/Main/DFData
Appendix 1 - How to collect 9500V PFM stats via the GUIStep 1
Turn on PFM collection
Step 2 Get configuration output
Step 3 Get PFM statistics
Appendix 2 - How to collect AMS/WMS PFM stats via the GUIStep 1
Turn on PFM collection
Step 2 Get configuration output
Step 3 Get PFM statistics
Appendix 3 - How to collect AMS2100/2300/2500 PFM stats via the
GUI HSNM2 Version 8.x and aboveIf you are using an old version of
HSNM2, refer to the procedures later in this Appendix. Step 1 Open
the array from HSNM2 GUI and select Performance > Monitoring
Click Change Measurement Items if data collection is not Enabled
for all items.
Make sure all items are checked and then click OK. Now click Get
Performance on the Performance > Monitoring GUI.
Step 2 Get PFM statistics
Make sure all items in the top part of the GUI are checked
Change Performance Measurement Mode to Auto Leave Interval set to 1
minute Change Number of repetitions to be 60 Click Start
Date collection will start.
When data collection has finished, click Get Files.
Save the ZIP file on your PC and upload it to TUF.
Step 3 Get configuration output
Click Open Advanced Settings.
Click Configuration Settings > Constitute and then click
Set.
Output all configuration items as TXT files. Choose an
appropriate name for each text file. Zip up all the text files and
upload them to TUF.
Old Versions of HSNM2 onlyStep 1 Open the array from HSNM2 GUI
and select Advanced Settings
Turn on PFM collection (if required)
Click Set.
Select all categories. Click OK. Step 2 Get PFM statistics Click
Output Text File. The following GUI will then be displayed.
Note: C:\Work is a directory on the HSNM2 server not on your
laptop/desktop!
If you use HSNM2 CLI on your workstation, the data will be
output to your workstation. This will make it easy for you to
upload the data to TUF. Step 3 Get configuration output
Output all configuration items as TXT files. Choose an
appropriate name for each text file. Zip up all the text files and
upload them to TUF.
