| Agents Administration - Tests |
|---|
|
Configuration of EMCPvMeCtlTest The storage controller is essentially a server that's responsible for performing a wide range of functions for the storage system. Each controller has an I/O path to communicate to the storage network or the directly-attached servers, an I/O path that communicates to the attached storage devices or shelves of devices, and a processor that handles the movement of data as well as other data-related functions, such as RAID and volume management. In the modern data center, the performance of the storage system can be directly impacted (and in many cases determined) by the speed and capabilities of the storage controller. If the controller or its processor is unable to meet the I/O processing demands of the infrastructure they support, then slowdowns will become a norm, and user complaints will become routine. Under such circumstances, IT administrators will seriously consider switching to alternative storage solutions with more robust controllers and high processing power. To avoid this eventuality, administrators need to keep checking on overall controller performance and processor usage from time to time, so that they can spot a potential I/O overload condition or a processing delay or a CPU contention before user experience is affected, and fine-tune cache usage, processor capacity, and/or the load-balancing algorithm of the controller to ensure peak performance of the storage system at all times. The EMCPvMeCtlTest helps administrators in this regard. This test auto-discovers the controllers of the EMC PowerVault ME storage system, monitors the I/O processing ability of each controller, and reveals the following:
The answers to these questions indicate how healthy each controller is and provide pointers to right-size the processor and controller cache (if needed). The default parameters associated with this test are:
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. |