Configuration of RaidctlTest

This test reports the current state of each RAID volume on the Solaris server, and thus brings to light those volumes that have failed, missing, or in a degraded state. By pointing administrators to real/probable abnormalities in the RAID volumes, the test prompts administrators to quickly initiate pre-emptive action and prevent the imminent data loss.

The default parameters associated with this test are:

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

• Specify the the host name of the server for which the test is to be configured in the HOST text box.

• Specify the port on which the server is listening in the PORT text box.

• By default, the USE SUDO parameter is set to No. This indicates that, by default, this test will report the health of every RAID volume by executing the raidctl –l command on each disk mirror. However, in some highly secure environments, the eG agent install user may not have the permissions to execute this command directly. In such cases, do the following:

  • Edit the SUDOERS file on the target host and append an entry of the following format to it:

    <eG_agent_install_user> ALL=(ALL) NOPASSWD: <Command>

    For instance, if the eG agent install user is eguser, then the entry in the SUDOERS file should be:

    eguser ALL=(ALL) NOPASSWD: raidctl –l

  • Finally, save the file.

  • Then, when configuring the test using the eG admin interface, set the USE SUDO parameter to Yes. This will enable the eG agent to execute the sudo raidctl –l command and retrieve the desired metrics.

• The SUDO PATH is relevant only when the USE SUDO parameter is set to ‘Yes’. By default, the SUDO PATH is set to none. This implies that the sudo command is in its default location - i.e., in the /usr/bin or /usr/sbin folder of the target Solaris host. In this case, the eG agent automatically runs the raidctl –l command with sudo from its default location, once the USE SUDO flag is set to Yes. However, if the sudo command is available in a different location in your environment, you will have to explicitly specify the full path to the sudo command in the SUDO PATH text box to enable the eG agent to run the sudo command.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will 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.