Agents Administration - Tests
 

Configuration of OraExaPhyDisTest

This test auto-discovers the physical disks on the target Oracle Exadata Storage Server and reports the status of each physical disk. Using this test, administrators can not only identify failed disks, but can also predict potential failure of a disk, so that efforts can be undertaken to avert the same. This test also reports the count of LUNs provisioned using each physical disk.

This page depicts the default parameters that need to be configured for the OraExaPhyDisTest test.

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

  • In the HOST text box, specify the IP address of the host for which this test is to be configured.

  • In the PORT text box, specify the port number at which the specified HOST listens. By default, this is NULL

  • 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.

  • Confirm the PASSWORD by retyping it in the CONFIRM PASSWORD text box.

  • 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.

  • Specify the time duration for which this test should wait for a response from the storage system in the TIMEOUT text box. By default, this is 120 seconds.

  • Once the above values are provided, click on the UPDATE button to register the changes made.

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.