Pre-requisites for Monitoring RHEV

General Pre-requisites

  • Enable the remote agent to communicate with the eG manager port (default: 7077).
  • If VMs running on multi-byte operating systems are to be monitored (eg., Windows Japanese), then the remote agent monitoring such VMs should also run on a multi-byte operating system.
  • 32-bit VMs that are to be monitored in an agentless manner should be configured with at least 2 GB RAM, and 64-bit VMs require at least 4 GB RAM. If more than four RHEV Hypervisors are being monitored in an agentless manner, then the RAM capacity of the VMs should be increased proportionately.

Pre-requisites for Obtaining the "Outside View" of VMs by connecting to the RHEV Manager

  • Ensure that the remote agent has IP connectivity to the RHEV manager.
  • Ensure that the remote agent has HTTP/HTTPS access to the port (port 8080/8443) at which the RHEV manager listens
  • All the tests that the remote agent executes should be configured with the name and password of a user with read-only access to the REST API of the RHEV manager. To know how to configure a read-only role on the RHEV manager and assign that role to a user, follow the steps detailed in Configuring the eG Agent to use the RESTful APIs on the RHEV Manager to Obtain the “Outside View” .

Pre-requisites for Obtaining the "Inside View" of Windows VMs, using the eG VM Agent

Pre-requisites for Obtaining the "Inside View" of VMs, without using the eG VM Agent

  1. Ensure that the remote agent has IP connectivity to at least one of the network interfaces of the VMs.
  2. The admin$ share should be enabled for all Windows-based virtual guests being monitored and the administrative account must have permissions to this share drive. Refer to Enabling ADMIN$ Share Access on Windows Virtual Guests for a step-by-step procedure to achieve this.
  3. To enable the remote agent to communicate with the Windows VMs, an administrative account login and password (either a local account or a domain account) must be provided when configuring the eG monitoring capabilities. 
  4. In case of VMs with the Windows XP/Windows 2003/Windows 2008/Windows Vista/Windows 7 operating systems, the firewall on the guest should be explicitly configured to allow Windows File and Print Sharing services which are required for the remote agent to communicate with the guest operating system.
  5. For monitoring a Windows VM, TCP port 139 must be accessible from the remote agent to the VM.
  6. For monitoring a Linux VM, the SSH port (TCP port 22) must be enabled for communication between the remote agent and the VM being monitored.


    If the Linux VMs in your environment listen on a different SSH port, then, you can override the default SSH port of 22 using the steps provided below:

    • Login to the eG manager.
    • Edit the eg_tests.ini file(in the <EG_INSTALL_DIR>\manager\config directory) on the eG manager host.
    • In the [agent_settings] section of the file, set the JavaSshPortForVm parameter to an SSH port of your choice. By default, this parameter is set to 22.
    • If your environment consists of multiple Linux VMs, each listening on a different SSH port, then, you can specify a comma-separated list of SSH ports against the JavaSshPortForVm parameter. For example: 7711,7271,8102
    • Finally, save the file.
  7. "inside view" of VMs running Windows Vista/Windows 7/Windows 2008 operating systems, the eGurkhaAgent service of the eG remote agent should be configured to run using domain administrator privileges. Refer to the eG User Manual for the procedure. For obtaining the "inside view" of other Windows VMs however, the remote agent service requires no such privileges.
  8. Set the inside view using flag for all the “inside view” tests to Remote connection to VM (Windows).