This test helps isolate which virtual networks are healthy and are too busy trafficking data to and from VMs, and which virtual networks are experiencing error conditions.

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 number at which the specified host listens in the PORT text box.

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.

• By default, this test communicates with every VM remotely and extracts “inside view” metrics. Therefore, by default, the INSIDE VIEW USING flag is set to Remote connection to VM (Windows). Typically, to establish this remote connection with Windows VMs in particular, eG Enterprise requires that the eG agent be configured with domain administrator privileges. In high-security environments, where the IT staff might have reservations about exposing the credentials of their domain administrators, this approach to extracting “inside view” metrics might not be preferred. In such environments therefore, eG Enterprise provides administrators the option to deploy a piece of software called the eG VM Agent on every Windows VM; this VM agent allows the eG agent on the service console to collect “inside view” metrics from the Windows VMs without domain administrator rights.To ensure that the “inside view” of Windows VMs is obtained using the eG VM Agent, set the INSIDE VIEW USING flag to eG VM Agent (Windows). Once this is done, you can set the DOMAIN, ADMIN USER, and ADMIN PASSWORD parameters to none.

• By default, 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 VMs 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 VMs. 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 do not belong to any domain (as in the case of Linux/Solaris guests) : In this case, 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. Then, proceed to provide the password of the ADMIN USER against ADMIN PASSWORD, and 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 the INSIDE VIEW USING flag is set to ‘eG VM Agent (Windows)’ - In this case, the inside view can be obtained without domain administrator privileges. Therefore, set the DOMAIN, ADMIN USER, and ADMIN PASSWORD parameters to none.

• While monitoring an RHEV Hypervisor, the REPORT_BY_USER flag is set to NO by default, indicating that by default, the VMs on the RHEV Hypervisor are identified using the hostname specified in the operating system. On the other hand, while monitoring RHEV Hypervisor - VDI environments, this flag is set to YES by default; this implies that in case of VDI servers, by default, the guests will be identified using the login of the user who is accessing the guest OS'.

• In case of both the RHEV Hypervisor and RHEV Hypervisor - VDI models, the REPORT_POWERED_OS flag is set to Yes by default. This flag is closely related to the REPORT_BY_USER flag. As already mentioned, the REPORT_BY_USER flag is set to No by default for an RHEV Hypervisor. As long as the REPORT_BY_USER flag is set to No, the eG Enterprise system will disregard the status of the REPORT_POWERED_OS flag (be it Yes or No), while monitoring the RHEV Hyperivsor. In other words, for the RHEV Hypervisor model, this test will continue to report measures for every powered-on VM on the server.

  In case of the RHEV Hypervisor VDI model however, the REPORT BY USER flag is set to Yes by default. In this case therefore, the default Yes status of the REPORT POWERED OS flag implies that this test will report measures for even those VMs that do not have any users logged in, as long as the VM is powered-on. Such guests will be identified by their virtual machine name and not the user name. If the status of this flag is changed to No instead, then this test will not report measures for those powered-on VMs to which no users are logged in currently.

• Administrators of some high security environments might not have permissions to internally monitor one/more VMs. The eG agent can be configured to ignore such ‘inaccessible’ VMs using the IGNORE VMS parameter. Against this parameter, you can provide a comma-separated list of VM names, or VM name patterns, for which the inside view need not be obtained. For instance, your IGNORE VMS specification can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside view of all VMs on an RHEV Hypervisor host by default.

  Note:

  While performing VM discovery, the eG agent will not discover the operating system of the VMs configured in the IGNORE VMS text box.

• By default, the eG agent does not support the inside view for VMs executing on Windows NT operating systems. Accordingly, the IGNORE WINNT flag is set to Yes by default.

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