|
Configuration of OraExaAlertTest
This test reports the count of alerts generated by the target Oracle Exadata Storage Server. Using this test, administrators can figure out how many critical, informational and warning alerts were generated. This will help administrators in proactively detecting issues in the target storage server and rectify them before any serious issues occur. Administrators can use the detailed diagnostics to figure out which alert was frequently generated and can use the alert message to identify the potential issues.
This page depicts the default parameters that need to be configured for the OraExaAlertTest test.
By default, this test uses the Cell Control Command-Line Interface (CellCLI) to pull out the required metrics. To use the CLI, the test first needs to connect to the target storage server via SSH, and then run commands using CLI. For running the commands, this test requires the credentials of a cellmonitor user. Specify the login credentials of such a user in the USERNAME and PASSWORD text boxes.
This test uses the Cell CLI to pull metrics from the target Oracle Exadata Storage Server. To run the CLI commands, this test first needs to establish an SSH connection with the target storage server. To enable the test to establish this connection, specify the SSH PORT in this text box.
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic 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:
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.
|