|
Configuration
of HpEvaVDiskTest
The HpEvaVDiskTest auto-discovers the LUNs on an EVA storage array, tracks the I/O requests to each LUN, and reveals how well the cache services these requests.
The parameters of this test are as follows:
-
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.
-
To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional DETAILED DIAGNOSIS capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the ON option. To disable the capability, click on the OFF option.
The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
- The eG manager license should allow the detailed diagnosis capability.
- Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
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.
|