Default Parameters for DiskSpaceTest

The DiskSpaceTest reports the space utilization of each of the disk partitions of a system.

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

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

• Set the DISCOVER NFS flag to Yes, if you want the test to automatically discover NFS drives on your system and report their status as well. By default, this flag is set to No. This flag is applicable for Windows 7 and Windows 2008 operating systems only.

• The DOMAIN, DOMAIN USER, and DOMAIN PASSWORD parameters are applicable to Windows systems only. When monitoring a Windows system, if the DISCOVER NFS flag of this test is set to Yes, then the test should be configured with the privileges of a valid domain user in order to auto-discover NFS drives and report their usage and status. In such a case therefore, specify a valid Windows domain name against DOMAIN, provide the name of a valid user in that domain against DOMAIN USER, and specify the password of that user against PASSWORD. Once the domain user credentials are provided, the test auto-discovers all those NFS drives on the target Windows system to which the configured domain user has access.

• Retype the PASSWORD of the configured domain user in the CONFIRM PASSWORD text box.

• Specify the maximum duration (in seconds) for which the test will wait for a response from the server in the TIMEOUT text box. The default timeout period is 30 seconds.

• Against the EXCLUDE parameter, you can provide a comma-separated list of disk partitions that you want to exclude from monitoring. For example, on Unix systems, you can use this parameter to exclude temporary partitions that the Unix system itself creates from monitoring.

• The USE SUDO parameter applies only to Linux and Solaris systems. By default, the USE SUDO parameter is set to No. This indicates that, by default, this test will report metrics by executing the df -Pk –l command on the Solaris host. 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: df –Pk -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 df –Pk –l command and retrieve the desired metrics.

• This parameter 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 df -Pk –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.

• Once the above value is provided, click on the Update button to register the changes made.

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.