Pre-requisites for Monitoring the Oracle VM Manager and its VMs
The following requirements should be set in place before attempting to monitor the Oracle VM Manager.
- 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.
Pre-requisites for Auto-Discovering the VMs on an Oracle VM Server
To enable the eG agent to auto-discover the IP address and operating system of the VMs on the Oracle VM server, make sure that the Windows PV driver is installed on each VM.
Pre-requisites for Collecting the ‘Outside View’ Metrics
To obtain the outside view of VM performance, the following pre-requisites should be fulfilled:
- Ensure that the remote agent has IP connectivity to the Oracle VM Manager.
- Ensure that the remote agent has web access to the WebPort (default port:7002)configured for the Oracle VM Manager.
- All the tests that the remote agent executes should be configured with the IP address of Oracle VM Manager and the name and password of a user withAdmin rights to the Oracle VM Manager.
Pre-requisites for Collecting the ‘Inside View’ Metrics from Windows VMs
To enable the eG agent to connect to a Windows VM and pull out ‘inside view’ metrics from it, you need to configure the eG agent with domain administrator privileges. In environments where administrators prefer not to expose the credentials of a domain administrator, a proprietary eG VM Agent software can be installed on each Windows VM to be monitored, which will enable the eG agent to obtain the ‘inside view’ without domain administrator permissions. The pre-requisites for obtaining the ‘inside view’ will therefore depend upon the how the Windows VMs are monitored – using the eG VM Agent? Or without using the eG VM Agent?
Pre-requisites for Obtaining the ‘Inside View’ of VMs, without using the eG VM Agent
- Ensure that the remote agent has IP connectivity to at least one of the network interfaces of the VMs.
- The admin$ share should be enabled for all Windows VMs being monitored and the administrative account must have permissions to this share drive. Refer to Section 1.2 of this document for a step-by-step procedure to achieve this.
- 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.
- In case of VMs with the Windows XP/Windows 2003/Windows 2008/Windows Vista/Windows 7/Windows 2012 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.
- For monitoring a Windows VM, TCP port 139 must be accessible from the remote agent to the VM.
- For obtaining the "inside view" of VMs running Windows Vista/Windows 7/Windows 2008/Windows 2012 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.
- Set the inside view using flag for all the “inside view” tests to Remote connection to VM (Windows).
Pre-requisites for Obtaining the "Inside View" of Windows VMs, using the eG VM Agent
- Install the eG VM Agent on each Windows VM. For details on how to install the eG VM Agent, refer to Section 1.3 of this document.
- Enable the remote agent to communicate with the port at which the eG VM Agent listens (default port: 60001).
- Set the inside view using flag for all the “inside view” tests to eG VM Agent (Windows).
Pre-requisites for Obtaining the ‘Inside View’ of Linux VMs
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.