XIV Performance Monitoring Tools
anthonyv 2000004B9K Comment (1) Visits (12134)
The IBM XIV has some great performance monitoring tools. These include:
The historical performance information is a great source of data and the XIV GUI has some very clever ways to display this data. However you may want to offload these statistics to a spreadsheet. The XCLI allows you to offload stats using a command that is formatted like the one below. This particular example will collect 1440 minutes (24 hours) of statistics in 1 minute intervals starting from midnight on November 6, from the XIV at IP address 10.10.1.10 piping the output to a CSV file.
xcli.exe -m 10.10.1.10 -u admin -p adminadmin -s statistics_get star
However the subsequent output may require further manipulation before it can be used. So we have produced a tool, structured very much like the configuration collection tool I described here, that will help you produce a very useful report.
Here is what you need to do:
1) Download XIV Performance Report version 6.8 zip file from this link. Click where it says Downloading this file.
2) You will get a zip file with six files in it. Unzip them into a folder on a Windows workstation. The Windows workstation also needs the XIV GUI installed on it (actually you only need the XCLI, but the Windows version of the XIV GUI will give you that).
3) Of the six files you just unzipped, you first need to edit the file call
4) You need to edit the section that looks like this:
' ****** Edit this list of IP/names and user/password for your own configs myConfigs.Add "1", "-m 184.108.40.206 -u admin -p adminadmin" 'myConfigs.Add "2", "-m 220.127.116.11 -u admin -p adminadmin" 'myConfigs.Add "3", "-m 18.104.22.168 -u admin -p adminadmin" 'myConfigs.Add "4", "-m 22.214.171.124 -u admin -p adminadmin" 'myConfigs.Add "5", "-m 126.96.36.199 -u admin -p adminadmin"
Lets say you have two XIVs, the details for which are:
XIV1 : Management: IP 10.1.10.100 Userid: admin Password: passw0rd
So we edit the section I mentioned above and make it look like this:
' ****** Edit this list of IP/names and user/password for your own configs myConfigs.Add "1", "-m 10.1.10.100 -u admin -p passw0rd" myConfigs.Add "2", "-m 10.1.20.100 -u admin -p passw0rd"
Now save the file. You can ignore the addi
Unless you acquire another XIV, you will not need to edit this particular file again.
5) The default behaviour of the script is to collect performance stats for the previous 24 hours. If this is what you want, then you do not need to change anything else. Just proceed to step 6. If however you want to collect stats for a specific period, then you will need to edit the
REM ************ 2 options ahead, choose 1, leave the other in remark! *************** REM *** 1. set your own time frame *** REM edit the following line to the date you need. REM cscript xiv_
Firstly un-REM the line starting with cscript (this is the REM shown in red in the example above, which is then gone in the example below). Then REM the line for option 2 (as shown by the extra REM in the example below). You will then need to edit the time period shown in red below. The line
So we could change the 10 to a larger number to get more samples and change the start date and time to get a different time period. You can also change the resolution (from minutes to hours for instance) and interval size (from 1 minute to 10 minutes).
REM ************ 2 options ahead, choose 1, leave the other in remark! *************** REM *** 1. set your own time frame *** REM edit the following line to the date you need. cscript xiv_
Once you have finished editing, save the file and proceed to the next step.
6) Now double-click on the icon
Each sheet is already set up for filtering and contains nicely formatted data. The most common question I get regards what is a write hit (versus a write miss). I explain that here.
If a host or port does not appear, the simple reason is normally that there are no stats to report on that port, so no entry appears.
If you want to see an example of a report, I have one right here
If you have a look at the example (which is a bit extreme), you can easily spot some interesting workload patterns and issues:
Comments and suggestions very welcome!