| Agents Administration - Tests |
|---|
|
Default Parameters for EMCPvMeCtlStTest 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 overall health of the storage controller. In single-controller configurations, if the storage controller crashes, then the storage system as a whole will become inaccessible to users. This is why, it is good practice to go for dual-controller configurations. A dual-controller configuration improves application availability because in the unlikely event of a controller failure, the affected controller fails over to the surviving controller with little interruption to the flow of data. However, since fail over occurs automatically upon the failure of a controller, administrators may not even know why the primary controller failed or whether the secondary has taken over or not! This is when the EMCPvMeCtlStTest comes in handy! This test not only monitors the status of each controller in the EMC PowerVault ME storage system, but also promptly reports controller failures and the reason for the failure. In the process, the test also indicates whether the primary controller has failed over to the secondary or not. This page depicts the default parameters that need to be configured for the EMCPvMeCtlStTest.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test. |