Agents Administration - Tests
 

Configuration of NfsMountTest

Network File System protocol (NFS) is often used to share file systems between servers and clients. Often, if an NFS file system fails, the directories mapped to the NFS file system will be unavailable. Accesses to these directories/files will take a long time and ultimately fail. This could potentially result in application failures and outages. Hence, administrators need the capability to detect when an NFS file system is unavailable or is running out of space. The NfsMountTest provides administrators with this capability. This test should be executed on a system that is an NFS client - i.e., is mounting directories from remote servers. This test auto-discovers all NFS-mounted directories and in real-time monitors the availability and space usage of each of these directories. This test is supported only on Unix platforms (i.e., not on Windows). Only agent-based monitoring is supported. One set of records for each NFS mounted file system.

The default parameters associated with this test are as follows:

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

  • In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

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

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