The HpEvaVDiskGrpTest auto-discovers the LUN groups on an EVA storage array, tracks the I/O requests to each group, and reveals how well the cache services these requests.

The parameters of this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOSTtext box, the host name for which the test is to be configured has to be specified.

• The PORT text box refers to the port used by the EVA SAN device.The default port is 'null'.

• In the EVAPERFLOCATION text box, specify the full path of the directory in which the evaperf.exe has been installed.

• Provide the name of the EVA SAN array that has been configured for monitoring in the ARRAYNAME text box.

• The SSSULOCATION test uses the EVAPerf software component to auto-discover the LUNs on an EVA storage array. The EVA Lun Status test on the other hand uses the SSSU console to discover LUN names. During auto-discovery, the EVAPerf utility reports the WWN names of the LUNs. In contrast, the SSSU console reports the friendly names of the same LUNs.
  To ensure that these LUNs are represented using a uniform, consistent notation across the eG monitoring interface, you can optionally configure this test to use the SSSU console (instead of EVAPerf) to perform LUN discovery. This way, the names of LUNs will be the same for this test and the EVA Lun Status test. To enable LUN discovery via the SSSU console, configure the full path to the location of the SSSU.exe in the SSSULOCATION text box. If you prefer not to use SSSU.exe for LUN discovery and would rather use the EVAPerf component instead, then, set this parameter to none.

• In the TIMEOUT text box, indicate the duration (in seconds) for which this test should wait for a response from the storage device. By default, this is set to 60 seconds.

• Finally, click the Update button.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.