This week I had to take a look at some performance concerns on an EVA. I had to dust off the old EVAPerf skills and made some notes along the way which I thought I would share.
EVAPerf is a command line utility used to monitor the performance of an EVA. It can be used in a console mode for real time monitoring or have the output piped to a CSV file for future review.
To run EVAPerf you need to connect to the server its installed on, open up a command prompt and change the EVAPerf directory e.g. cd C:Program Files (x86)Hewlett-PackardEVA Performance Monitor. The key command to collect all performance stats and pipe them to a CSV is:
evaperf all -csv -cont <xx> -dur <yy> -ts2 > <outputfile>
all = collect all performance counters
-csv = make file CSV type
xx = the interval at which data is collected in seconds
yy= how long (the duration) the collection will run for in seconds
-ts2 makes the file follow Microsoft Time format
I was troubleshooting an issue which occurred at a particular time each day and so created a batch file with the commands below and scheduled it using Windows Task Scheduler.
FOR %%A IN (%Date:/=%) DO SET Today=%%A cd “C:Program Files (x86)Hewlett-PackardEVA Performance Monitor”evaperf all -csv -cont 60 -dur 3600 -ts2 >f:%Today%.csv
The above command will give you all performance counters, for a duration of one hour, will collect stats once a minute and pipe the results to a CSV file with the days date.
If you want to see which individual performance counters are available just type evaperf with no options and press enter, this will then give you a list of all the available commands you can use to monitor the EVA. Some of the most useful ones are:
evaperf pd = physical disks stats
evaperf vdg = virtual disk group stats
evaperf vd = virtual disk stats
evaperf hps = host port stats
evaperf cs = controller stats
To monitor in real time just enter any of these commands directly into the CLI.
To keep up to date with more news follow 3ParDude on Twitter
4 thoughts on “A Quick Guide to EVAPerf”
It would also be a good idea to edit the logging.conf file located in evaperf directory (now called eva Performance Monitor). This will give historical data regarding the performance of your EVA. The default is to keep history for 3 days. However, the files can be copied to another location for historical reference. The details for editing this file can be found in chapter 10 of the Command View users guide.
I haven’t had much luck in changing the retention days so I copy the files nightly to an alternate location. This is great in assisting the troubleshooting of intermittent issues.
When editing this file, at a minimum, change the per_logging from no to yes. Save the file, and restart the evaperf service (currently called HP P6000 Performance Data Collector). You will now be collecting historical performance data.
Excellent information. Thanks for taking the time to share.
hello, jogging my memory too :
there was also the poorly documented but VERY useful evaperv -vtds command, to show the transfers by block size for eah LUN.
that was quite useful to debug some strange service times.. (the HSV don’t like massive I/O greater than 128k)
Thanks for the useful comments. I have also come across the challenges with block sizes being greater than 128K and will write a blog post about it in the future.