Auditing Virtual Machines
You can discover and audit virtual machines using theHEAT Discovery virtual machine host auditorDiscovers and audits virtual machines. (VMHA). HEAT Discovery Managers can manage the virtual machine host auditor, gateway settings, and configurations.
|
The virtual machine host auditor is an advanced function for administrators that is only available in the Gateway Data Center Edition workspace. |
A virtual machine contains virtual hardware and, typically an operating system and software, in the same way that a physical machine consists of physical hardware, an operating system, and software. HEAT Discovery uses the guest/host model, which displays a host machine with a number of guests. For example, one physical computer can host a number of guest virtual machines.
For HEAT Discovery to obtain guest/host relationship information, you need to deploy the client agent to the physical host and virtual machine guests.
Auditing of the following virtual machines is supported:
- VMware Server Version 2
- VMware ESX Server 3.5
Using HEAT Discovery virtual machine host auditor you can:
- Audit a virtual machine and its host.
- Link the virtual machine to its host machine.
- View data related to the virtual machine.
Virtual machines with a network adapter configured as “host only” are not discovered or audited.
Discovering Virtual Machines
The virtual machine host auditor on the VMHA Configurations tab, is only available in the Gateway Data Center Edition workspace. You must first install and configure a gateway data center before you can access this functionality. See Installing a Gateway
| 1. | Open a Gateway workspace and double-click a gateway from the list to view the record. |
| 2. | Click the VMHA Configurations tab and select New VMHA Configuration. |
| 3. | Enter the server URL (or IP address) of the ESX or vCenter server that contains the virtual machines. |
For ESX servers, /sdk specifies the location of the interface that the client agent uses to audit the server. Change this only if the ESX server is configured to have a different location for the SDK.
If you enter a vCenter URL, then all ESX servers managed by that vCenter and all virtual machines in each ESX server are discovered.
ESX servers that run as appliances cannot have a client agent deployed to the appliance. For these, you must specify the host and administration credentials so that the client agent can remotely audit the ESX server to determine its guests.
| 4. | Enter the user name and password for accessing the server. In most cases you need the root or administrator name and password to gain access. |
| 5. | Click Save. |
| 6. | Repeat the process to add a configuration for each ESX or vCenter server. |
Deploying the Configurations
After you configure the virtual machine host auditor, do the following:
| 1. | Click Deploy Settings to send the configurations to the gateway. |
When the client agent receives the new gateway settings, it saves the relevant virtual machine host auditor settings to a file called C:\Program Files (x86)\Frontrange Solutions\SaaSIMClient\ClientAgent\Vmha\Vmha.xml and restarts the client agent services.
The scan results are saved in VMHost.xml and sent to the server.
| 2. | To locate the servers, from the CI workspace, group the configuration items by HEAT Discovery method. Locate the Discovery Method: VMHA group. The newly discovered servers are listed with an agent status of not installed. |
| 3. | Click on a server to view the details. |
| 4. | The Guest tab displays the number of virtual machines hosted by the server. Click the tab to display a list of virtual machines. |
You can now manually deploy client agents to the virtual machines.