You are on page 1of 3

VirtualCenter Guided Consolidation Service

VirtualCenter includes guided consolidation service that assists users to move their
servers running on physical machines to virtual machines seamlessly. This is a composite
service that relies on the presence of two other components: Data Collector Service, and
Virtualization Service. Data Collector Service is always installed on the same system as
the VirtualCenter, while Virtualization Service can be installed anywhere.

Data Collector Service is responsible from collecting configuration and statistical
performance data about the physical servers. It runs as a service on the machine, under
the name of “VMware Capacity Planner Service.” The data this service collects is then
used by the guided consolidation service to come up with a characterization of these
physical systems and get them to an appropriate place. Data Collector Service is
responsible from discovering existing systems in the environment, getting their hardware
information, and probing them periodically to collect their performance information. For
the discovery of such systems, either LAN Manager (Lanman) or Active Directory (AD)
is used. Due to reliance on Lanman or AD, the environment must have either of these,
and be set properly to allow the Data Collector Service perform its duties.

In the case of Lanman, the Data Collector Service needs individual systems to be visible
by Lanman, and that they are reported as present when polled. In the absence of Lanman
and presence of AD, the system where the Data Collector Service is installed must be part
of a domain (i.e., cannot be a standalone machine), and the user it is running as must have
read permissions on the AD. Discovery of systems is repeated periodically (albeit
infrequently) so that any system newly added to the environment can also be discovered

Configuration and performance data of discovered systems is retrieved periodically, with
the former being retrieved less frequently than the latter. The Data Collection Service is
agent-less, i.e., it does not install any software on target machines; but rather, it relies on
remote data retrieval methods (WMI, Remote Registry etc.). As such, it requires some
special configuration guidelines to be followed for the installation of this service as well
as the target (collected) machines. First, the Data Collector Service must run with
administrator privileges. Also, since the target systems are probed periodically remotely,
they should either not have a firewall or their firewall should be configured to allow
incoming WMI, Perfmon, Remote Registry requests to pass through (i.e., ports 135-139
and 445 should be left open).

Guided Consolidation Service generates recommendation based on the collected data as
well as the state of the ESX hosts in the inventory. The recommendation is made such
that the destination ESX host has sufficient resources to host the newly created virtual
machine, and is compatible in terms of hardware and software. Compatibility is
considered for things such as sufficient number of CPUs, ability to run the guest OS etc.
Disk space requirements of the system being virtualized are also taken into account. In
order to preserve disk space, disks of the systems being virtualized is shrunk such that the

unused space is not more than 25% of the used space. Try again later. For more documentation on this service please refer to http://www. but can not see any systems in any of the domains: In order for a domain to be probed for its systems. require to be installed on the same system as the VirtualCenter. If still nothing is visible: o Is it possible that the domain does not have any system in it? o Lanman could be instructed to have a system hidden. it could be the case that the Data Collection Service is not setup properly. VirtualCenter uses the VMware Converter Enterprise module as the Virtualization Service. This should be done by checking on “VMware Capacity Planner Service” (in services). it could take the Data Collection Service a few minutes for it to be able to collect. the Data Collector Service has not reported any domains to VirtualCenter yet. the system will not be visible to anyone.” This is caused because at the moment you clicked on either link. However. Troubleshooting Guide • I can not see any domains: In the “Consolidation” view.vmware. In the absence of both Data Collection Service can not function ƒ If you have AD rather than Lanman. however. when you click on either “Analyze physical computers for consolidation” in the “Getting Started” tab or “Start Analysis” button in “Analysis” tab. it has to be selected from the pulldown menu. ƒ Make sure you have either Lanman or Active Directory (AD) setup in your environment. The discovery of systems could take a few minutes. This will probe the domain for its systems. • I can see domains.pdf. and the Data Collection Service must run as a user with read privileges on the AD. the system where VirtualCenter (and the Data Collection Service) is installed must be in a domain. and converting it to a virtual machine. A basic test for this condition is visibility of such systems in the network neighborhood of the system where the Data Collector Service is installed. and hence requires VirtualCenter to be installed and running for its proper operations. This may take several minutes. no disk is shrunk to less than 4GB. Virtualization Service is responsible for importing a source machine. and making sure that it is running. It is designed to run as an extension of VirtualCenter. o If waiting for a few minutes did not solve the problem. In general any system that is . you may get a pop-up window with the message “VirtualCenter must gather more information to enumerate the domains and workgroups in the enterprise. In such a unless its original size was smaller. and more depending on the size of the domain. Wait for a few minutes and click the button again. It does not. o In general. and then the “GO” button needs to be pressed. ƒ Check to make sure that the Data Collector Service is installed and is running.

if any of the systems is successfully collected. This must be due to some recent activity on the ESX host that has shrunk the available disk space. For a collection to be successful. since the space requirements computations would consider only already allocated space. 139 and 445 must be left open for incoming connections. Note that the user should be able to read performance data. it must have been running at some point. run WMI and read the registry for it to be sufficient for data collection. Note that this can not be the case. o The Data Collection Service is not running with administrator privileges. It is an extension to VirtualCenter and is not a part of it. In order to collect data from remote systems. followed by some error message. • I selected systems. but some/all have failed to gather data: In this case. o The system being collected has a firewall. o The destination host (ESX host) does not have sufficient space to copy the file systems in the virtualized system. This is a limitation imposed by the underlying operating system. o A username/password without sufficient privileges is entered for the system being collected. 137. Common cases are: o The Virtualization Service is not installed. but the consolidation fails: Consolidation failure message should have sufficient information about the nature of the failure. More common cases of failure are: o The Data Collection Service is not running. The final product should recommend something like this. 138. o A bad username/password is entered for the system being collected. o The version of the ESX is not recent enough to run an OS of the system being virtualized. if any of the systems is successfully collected. the collector needs to run with administrator privileges. Note that this can not be the case. and not what is going to be allocated soon. It could also happen if simultaneous virtualizations were happening. but may be it was stopped. • I select a system and try to consolidate. Note that because the discovery was done. the systems will appear with some red triangle in the “Analysis” tab. ports 135. In general the error message should be explanatory. The Virtualization service should be installed separately. not visible in the network neighborhood cannot be discovered by Data Collection Service. . and the firewall does not have required ports open.