The VmgUptimeTest reports statistics pertaining to the uptime of the Windows and Linux guests configured on a host operating 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 PORT at which the HOST listens. By default, this is NULL.

• Specify the DOMAIN within which the virtual guests reside. If the guests belong to a specific domain, an administrative account in that domain can be provided in the ADMIN USER field. If the guests do not belong to any domain, specify "none" in the DOMAIN field, and specify a local administrator account name in the ADMIN USER below. Prior to this, you need to ensure that the same local administrator account is available or is explicitly created on each of the virtual machines to be monitored. On the other hand, if the guests belong to different domains, then 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.

• This test connects to each virtual guest and attempts to determine the resource usage of each of the guests. In order to do so, the test must be configured with user privileges that allow a remote connection to the virtual guest from the XenServer host or a remote Windows host (in the case of agentless monitoring). If the virtual guests are within a DOMAIN, then provide a domain administrator account name in the ADMIN USER text box. If the DOMAIN parameter is set to "none", then a local administrator account has to be specified in the ADMIN USER text box. Prior to this, you need to ensure that the same local administrator account is available or is explicitly created on each of the virtual machines to be monitored. In either case, the eG agent should be able to connect to each guest operating system. On the other hand, if the guests belong to different domains, then 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. To know how to create multiple VM users using the resulting page, follow the procedure detailed in the discussion on the DOMAIN parameter.

• The password of the ADMIN USER needs to be provided in the ADMIN PASSWORD text box. Here again, if multiple passwords need to be specified, then follow the procedure detailed in the discussion on the DOMAIN parameter.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box. Here again, if multiple passwords need to be specified, then follow the procedure detailed in the discussion on the DOMAIN parameter.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. Specify the default value 1:1 in the DD FREQUENCY text box. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying nonein this text box.

• The REPORTMANAGERTIME flag governs the shutdown and reboot times shown in the detailed diagnosis of this test. If this value is set to Yes, the shutdown and reboot times are displayed in the manager's time zone. If this value is set to No, the shutdown and reboot times are displayed in the time zone of the system where the agent is running (i.e., the system being managed for agent-based monitoring, and the system on which the remote agent is running - for agentless monitoring).

• To make diagnosis more efficient and accurate, the eG system 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, by default, for a particular server-type, choose the On option against DETAILED DIAGNOSIS. 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 bad and normal 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.