The VsgWinMemoryTest tracks critical metrics corresponding to the System PTEs and the pool areas of kernel memory of each virtual guest of an MS Virtual server.

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 PORT at which the HOST listens. By default, this is NULL.

• This test connects to each virtual guest remotely and attempts to collect "inside view" metrics. In order to obtain a remote connection, the test must be configured with user privileges that allow remote communication with the virtual guests. The first step towards this is to specify the DOMAIN within which the virtual guests reside. The ADMIN USER and ADMIN PASSWORD will change according to the DOMAIN specification. Discussed below are the different values that the DOMAIN parameter can take, and how they impact the ADMIN USER and ADMIN PASSWORD specifications:

  • If the VMs belong to a single domain : If the guests belong to a specific domain, then specify the name of that domain against the DOMAIN parameter. In this case, any administrative user in that domain will have remote access to all the virtual guests. Therefore, an administrator account in the given domain can be provided in the ADMIN USER field and the corresponding password in the ADMIN PASSWORD field. Confirm the password by retyping it in the CONFIRM PASSWORD text box.
• If the guests belong to different domains - In this case, you might want to provide multiple domain names. If this is done, then, to access the guests in every configured domain, the test should be configured with the required user privileges; this implies that along with multiple DOMAIN names, multiple ADMIN USER names and ADMIN PASSWORDS would also have to be provided. To help administrators provide these user details quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the Click here hyperlink that appears just above the parameters of this test in the test configuration page.In the page that appears next, specify the following:
  • First, provide the name of the Domain to which the VMs belong. If one/more VMs do not belong to any domain, then, specify 'none' here.
  • The eG agent must be configured with user privileges that will allow the agent to communicate with the VMs in a particular domain and extract statistics. If 'none' is specified against Domain, then a local administrator account can be provided against Admin User. On the other hand, if a valid Domain name has been specified, then a domain administrator account can be provided in the Admin User text box.
  • The password of the specified Admin User should be mentioned in the Admin Pwd text box.
  • Confirm the password by retyping it in the Confirm Pwd text box.
  • To add more users, click on the circled '+' button in the page. This will allow you to add one more user specification.
  • In some virtualized environments, the same Domain could be accessed using multiple Admin User names. For instance, to login to a Domain named 'egitlab', the eG agent can use the Admin User name labadmin or the Admin User name jadmn. You can configure the eG agent with the credentials of both these users by adding two separate specifications - one for the labadmin and another for jadmn in our example - for the same domain name using this page. When this is done, then, while attempting to connect to the domain, the eG agent will begin by using the first Admin User name of the specification. If, for some reason, the agent is unable to login using the first Admin User name, then it will try to login again, but this time using the second Admin User name of the specification - i.e., jadmn in our example. If the first login attempt itself is successful, then the agent will ignore the second Admin User name.
  • To clear all the user specifications, simply click the Clear button.
  • To remove the details of a particular user alone, just click the circled '-' button corresponding to the user specification.
  • To save the specification, just click on the Update button. This will lead you back to the test configuration page, where you will find the multiple domain names, user names, and passwords listed against the respective fields.

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