UCMDB Support Tip: VMWare Infrastructure Topology Discovery
As we had questions on how to discover VMWare infrastructure here are the steps you have to perform to do this:
1. Prerequisite - Set up protocol credentials:
The WMI, Shell (Telnet, SSH, NTCMD), and SNMP protocols are required to discover
hosts and host processes. These protocols require the user name, password, and domain name (the domain name is
optional for NTCMD).
The VMware Infrastructure Management (VIM) protocol is required for all VMware jobs.
This protocol requires a user name and password.
Port Number is optional.
Use SSL.true: select if the VMware servers are configured to use SSL by default. false:
select if the VMware servers are configured to use non-secured http.
2. Set up VMware Infrastructure permissions:
System.Read permissions for users performing discovery. Users should have permissions for all entities being discovered, and must have been assigned at least a Read-Only role.
Global.Licenses permissions to obtain the total and available number of licenses for each
License Feature. If the user does not have these permissions, these attributes remain
3. Run Host discovery To connect to each potential VMware server (vCenter, VirtualCenter, or ESX), discover its Host CI by running one of the Host Connection by Shell/WMI jobs.
4. Run Processes discovery To connect to each potential VMware server (vCenter, VirtualCenter, or ESX), you must discover Process CIs that match certain criteria, and run Application Signatures discovery by running one of the Host Applications by Shell/WMI jobs.
5. Run VMware Infrastructure discovery The Virtualization module includes two jobs for vCenter or VirtualCenter Server discovery and two for ESX Server discovery: a. If the VMware Infrastructure environment is managed by vCenter or VirtualCenter Servers, run the VMware vCenter Connection by VIM job, followed by the VMware vCenter Topology by VIM job. b. If the VMware Infrastructure environment includes unmanaged ESX servers (standalone) or the entire environment is unmanaged, run the VMware ESX Connection by VIM job, followed by the VMware ESX Topology by VIM job.
If you want more details you can check the Discovery and Integration Content Guide - Discovery Modules.
uCMDB Support Engineer
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”