The Perfstat GUI provides a user interface to the Performance and Statistics Collector (Perfstat) utility running in a Windows environment. It provides the means to configure the SSH infrastructure for Perfstat to run as well as executing Perfstat with specified parameters.
The Perfstat GUI consists of a single file (Perfstatgui.hta). There is an optional file (PerfstatScriptTemplate.vbs) to run Perfstat within a scripted configuration. Copy these files to the directory of your choice on a supported Windows system.
Perfstat GUI can be installed in any Windows environment that is currently supported by Perfstat (see the related Perfstat documentation for current supported environments).
Clustered ONTAP with Perfstat Converged Configuration –
1. Select the “Create Local SSH Key” option. This option sets up OpenSSH for Windows and prepares a SSH key to utilize in conjunction with Perfstat. Before executing ensure the OpenSSH.zip file
(downloaded from http://support.netapp.com/NOW/download/tools/perfstat/OpenSSH.zip) exists in the same directory as the Perfstat GUI. This option only needs to be performed a single time. If you attempt to run it again the GUI will detect that a local key already exists.
2. Each NetApp controller that you wish to run Perfstat against will need to have the SSH keys copied
to it. This only needs to be performed a single time for each controller. To perform this step select
the option “Copy Local SSH Key to a Clustered NetApp Controller”. This will copy the SSH key to each controller in the cluster. Complete the cluster and user information. Click on the “Copy via
SSH” button, and then when prompted enter the password to access the NetApp cluster to complete the copy.
3. To execute the system shell commands section of Perfstat, each NetApp controller will need to have the diag user unlocked and a password set. To perform this task select the “Prepare Diag Account on NetApp Controller” option. Enter the controller name or IP address and click on the Run button.
You will be prompted to enter a password for the diag user (it must follow the security rules you
have configured on the NetApp controller.
4. Download the current Perfstat Converged version from http://support.netapp.com/NOW/download/tools/perfstat/perfstat8.shtml and plink executable from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and place the
downloaded files into the same directory as the Perfstat GUI. If you have any issues with the plink.exe consult the plink download site for the “latest development snapshot”.
5. For a simplified set of arguments for Perfstat to operate select the “Run Perfstat Converged with
Basic Options” option. If you desire to complete set of arguments for Perfstat select “Run Perfstat
Converged with All Options”. For the basic options, the most typical fields are presented while the
“all options” provides every available argument in Perfstat. Hover over any of the fields for description of the field. Refer to Perfstat documentation for more information on each field. When
the fields you desired are completed click on the “Execute Perfstat” button. A new command
window will open with Perfstat executing inside.
6. When complete the results file will be in the “OpenSSH\Bin” subdirectory of the directory as the
Perfstat GUI with a .zip extension. Select the “Upload File to NetApp” option and a full list of results
files will be presented along with the link to the NetApp upload site.
7. There is an optional script that can be used when you want to run Perfstat outside of the GUI (i.e. as a scheduled task). The script can be configured to either run a single time or to run indefinitely with a new Perfstat launching when the previous one completes.
To create a script, download the PerfstatScriptTemplate.vbs in the same directory as the Perfstat GUI. Then within the “Run Perfstat Converged with All Options” option select the checkbox for “Create Script Only”. The output in the Perfstat GUI will give you a line to add to the .vbs file along with basic configuration instructions. It is suggested to run Perfstat at least once without the “Create Script Only” option to ensure all settings are functioning correctly.