Pre-requisites for Monitoring the Oracle VirtualBox in an Agentless Manner
- 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 VMs and Obtaining their Outside View
- Ensure that the remote agent has IP connectivity to the target VirtualBox.
- Ensure that the remote agent can connect to the target VirtualBox via SSH.
- Configure all the tests that the remote agent executes with the name and password of a user who is privileged to access the VirtualBox via SSH.
- To enable the remote agent to run VDA commands on the VirtualBox, a sudo package has to be installed on the VirtualBox host; to know how to install the sudo package, refer to Pre-requisites for Auto-Discovering VMs and Obtaining their Outside View.
After the sudo package is installed, perform the following steps on the VirtualBox host:
- Login to the host as a root user;
At the command prompt of the host, issue the following command to create a new user:
useradd –d /export/home/<username> –m <username>
useradd –d /export/home/eguser –m eguser
Next, issue the following command to set a password for the above user:
- When prompted to provide the password, specify the same.
Then, proceed to edit the sudo script by issuing the following command:
Add the following entry to the script:
- All the tests run by the eG agent should be configured with the full path to the install directory of the sudo package;
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 Configuring the eG Agent to Obtain the Inside View of Windows VMs, using the eG VM Agent.
- 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 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-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.
- 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 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 on the vSphere/ESX host to communicate with the guest operating system. Refer to Configuring Windows Firewalls to Allow File and Print Sharing for a detailed procedure.
- For monitoring a Windows VM, TCP port 139 must be accessible from the remote agent to the VM.
- For monitoring a Linux/Solaris VM, the SSH port (TCP port 22) must be enabled for communication between the remote agent and the VM being monitored.
- For obtaining the "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. 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).