Agents Administration - Tests
 

Configuration of PVSRamCacheTest

This test helps administrators keep tabs on the usage of the write-cache of every target device that is connected to the Provisioning server, and sends out proactive alerts to administrators if it finds that a write-cache file is rapidly filling up. In addition, this test promptly captures I/O transaction failures and reports the number of times each target device had to retry an I/O transaction on the PVS.

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.

  • The port number to which the server is listening is to be provided in the PORT text box. By default, this is 54321.

  • This test executes commands using the Management Command Line Interface (MCLI) of the Provisioning server to collect the required metrics. To enable the test to execute the commands, the eG agent, by default, auto-discovers the full path MCLI.exe on the target Provisioning server. This is why, the MCLI PATH is set to none by default. If, for some reason, the eG agent is unable to auto-discover the MCLI path, then you will have to manually specify the path here using the following pointers:

    • Typically, in a 32-bit Windows system, the MCLI.exe will be available in the following location by default: <System_Root>\Program Files\Citrix\Provisioning Services Console
    • In a 64-bit Windows system on the other hand, the MCLI.exe will be available in the following location by default: <System_Root>\Program Files (x86)\Citrix\Provisioning Services Console

  • To report farm-related metrics, this test should run using the credentials of a user who fulfills the following requirements:

    • Should belong to a Security group with ‘Farm Administrator’ access.

    • Should be assigned the Allow log on locally security privilege on the Provisioning server host.

    To know the steps for assigning such privileges to a user, click here.

    Once you assigned the aforesaid previleges to the user, then configure this test with the DOMAIN NAME, DOMAIN USER, and DOMAIN PASSWORD of the same user.

  • By default, the LOCAL HOST ONLY flag is set to No. This implies that, by default, the test auto-discovers all the servers that are part of the PVS farm, and reports metrics for each server. Setting the flag to Yes ensures that the test reports metrics for only that server, which is being monitored.

  • By default, the SHOW ACTIVE TARGETS ONLY is set to Yes, indicating that the test will monitor only those target devices that are up and running currently, by default. To enable the test to monitor all devices, regardless of their running state, set this flag to No.

  • To make diagnosis more efficient and accurate, the eG Enterprise suite 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:

    • The eG manager license should allow the detailed diagnosis capability;
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

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