VMware VCENTER APPLICATION DISCOVERY MANAGER 6.1.1 - RESPOSITORY, User Manual

Page: 50 / 74

ADM User’s Guide
50 VMware, Inc.
Use Case
The following use case describes the typical flow for passive and detail discovery of a VMware environment.
Assumptions
Assumptions for both passive and detail VMware Infrastructure discovery are as follows:

The VMware Infrastructure components (VMware Infrastructure 3 or higher, VMware Virtual Center and
VMware ESX Server) are properly configured and operational. VMware Virtual Center is used for
management.

A web interface or Virtual Infrastructure Client (VIC) is used for interfacing with VMware Virtual Center.
(A VIC is a front ‐ end UI client used to administer Virtual Center. It is either a Windows application or a
web application.)

One of the following protocols is allowed in the VMware Infrastructure environment:

SSH/Telnet/SNMP on the VMware ESX Server.

VI ‐ SDK with either Virtual Center or all of the ESX Server in the VMware Infrastructure environment.

You have the credentials to log in to the target machine using the SSH, Telnet, SNMP, or VI ‐ SDK protocols,
and these credentials allow you to access information about virtual machines.

For detail discovery of VMware environments, it is assumed that Virtual Center hosts have already been
discovered with passive or IP discovery.
Player (service) Product, vendor, and version. Telnet, SSH, WMI
VM ‐ Tools (installed
software)
Product, vendor, and version.
Note: VM ‐ Tools is an attribute of the guest OS, not the virtual machine
configuration.
Telnet, SSH, WMI
Table 5-4. Discovered VMware Components and CIs (Continued)
Component (CI type) CI Discovery Method