This test periodically monitors the memory usage of the hypervisor, checks whether adequate free memory is available to the hypervisor, and if not, promptly alerts users to the same.

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.

To auto-discover the VMs on a target RHEV hypervisor and obtain the outside view of the performance of each VM, the eG agent needs to connect to the RHEV Manager that manages the target RHEV hypervisor. To enable the eG agent to obtain the outside view, you need to configure the test with the following:

• Specify the IP address/host name of the RHEV Manager that the eG agent should connect to in the RHEL MGR HOST text box.

• Specify the port number at which the said RHEV Manager listens in the RHEL MGR PORT text box.

• Specify the domain to which the RHEV Manager belongs in the RHEL MGR DOMAIN text box.

• In the RHEL MGR USER and RHEL MGR PASSWORD text boxes, specify the credentials of the user with read-only access to the Restful API on the RHEV manager. To know how to create a read-only role and assign it to a user, Click here.

  If the RHEV hypervisor being monitored was discovered via an RHEV Manager, then the IP address, port number, domain name, and user credentials of the RHEV Manager used for discovery will be automatically displayed against the respective parameters.

  If the RHEV hypervisor being monitored was not discovered via an RHEV Manager, but you still want to use an RHEV Manager for obtaining the outside view, then, you can select any IP address of your choice from the RHEL MGR HOST list. By default, this list will be populated with the IP addresses/host names of all the RHEV Managers that were configured for the purpose of discovering the RHEV hypervisors. If you select an RHEL MGR HOST from this list, then the corresponding port number, domain name, and user credentials will be automatically displayed against the respective parameters.

  On the other hand, if the RHEV Manager that you want to use for metrics collection is not available in the RHEL MGR HOST list, then, you can configure an RHEV Manager on-the-fly by picking the Other option from the RHEL MGR HOST list. An ADD THE RHEV MANAGER DETAILS window will then pop up. In the pop up window specify the following:

  • Specify the IP address/host name of the RHEV Manager that you wish to add in the RHEV Manager identity text box.

  • Set Use SSL to connect to RHEV Manager flag to Yes if the RHEV manager in your environment is SSL-enabled. Otherwise, set this flag to No.

  • If the RHEV Manager is SSL-enabled, then 8443 will be displayed in the Manager Port text box by default. On the other hand, if the manager is not SSL-enabled, the default Manager Port will be 8080. If the RHEV manager in your environment listens on a different SSL or non-SSL port, then make corresponding changes to the default setting.

  • If you also want to discover additional RHEV servers in your environment using this RHEV manager, set the Discover RHEV Hypervisors using this RHEV manager flag to Yes. If you only want to use this RHEV manager to obtain the outside view of VMs, set this flag to No.

  • In the Username to connect to RHEV manager and Password for user text boxes, specify the credentials (i.e., user name and password) of a user who has been assigned read-only access. To know how to create a read-only role and assign it to a user, Click here.

  • Confirm the password by retying it in the Confirm password for user text box.

  • Specify the domain to which the RHEV Manager belongs to in the Domain name for the RHEV Manager text box.

• Confirm the RHEL Manager password by retyping it in the CONFIRM PASSWORD text box.

• By default, the RHEV Manager is SSL-enabled. Accordingly, the SSL flag is set to Yes by default. This indicates that the eG agent will communicate with the RHEV Manager via HTTPS by default.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. 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 none against DD FREQUENCY.

• 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 for a particular server, 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.