vCenter data collected

Discovery identifies and classifies information about VMware vCenter servers.

vCenter table schema

The vCenter table schema is illustrated in the following diagram:

Figure 1. vCenter table schema
vCenter table schema
Several tables are cloud-agnostic tables, meaning that they can be populated for any cloud resource, not just vCenter resources. Look in the subtables that extend the cloud-agnostic tables to find discovered CIs.
Cloud-agnostic table Look in this vCenter-specific table
Virtual Machine Instance [cmdb_ci_vm_instance] VMware Virtual Machine Instance [cmdb_ci_vmware_instance]
Operating System Template [cmdb_ci_os_template] VMware Virtual Machine Template [cmdb_ci_vmware_template]
Logical Datacenter [cmdb_ci_logical_datacenter] VMware vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Cloud Networks [cmdb_ci_network] VMware vCenter Network [cmdb_ci_vcenter_network]
Datastore [cmdb_ci_datastore] VMware vCenter Datastore [cmdb_ci_vcenter_datastore]
Host Cluster [cmdb_ci_host_cluster] VMware vCenter Cluster [cmdb_ci_vcenter_cluster]

vCenter data

Discovery uses multiple vCenter probes to collect this data from vCenter. The data is saved in several tables.

Table 1. VMware vCenter Instance [cmdb_ci_vcenter]
Field label Column name
Name name
Full name fullname
Instance UUID instance_uuid
URL url
Effective CPU effectivecpu
The combination of the vCenter instance in the cmdb_ci_vcenter table and the object ID in the cmdb_ci_vm_object table identifies a specific vCenter.

The tables extend from the Virtual Machine Objects [cmdb_ci_vm_object] table, which holds object IDs for all cloud-based resources, except virtualization servers.

Table 2. VMware Virtual Machine Instance [cmdb_ci_vmware_instance]
Field label Column name
Name name
Template template
CPUs cpus
Disks disks
Disks size (GB) disks_size
Memory (MB) memory
Network adapters nics
Image path image_path
State state
vCenter Instance UUID vcenter_uuid
vCenter Reference vcenter_ref
Base name base_name
VM namer vm_namer
BIOS UUID bios_uuid
VM Instance UUID vm_instance_uuid
Table 3. VMware Distributed Virtual Port Groups [cmdb_ci_vcenter_dv_port_group]
Field Label Column name
Name name
vCenter Instance UUID vcenter_uuid
Distributed Virtual Switch Reference dvs_ref
Table 4. Operating System Template [cmdb_ci_os_template]
Field Label Column name
Image Type image_type
Guest OS guest_os
Status status
Root Device Type root_device_type
Image Source image_source
Table 5. VMware Virtual Machine Template [cmdb_ci_vmware_template]
Field label Column name
Name The template name from VMWare.
CPUs cpus
Disks size (GB) disks_size
Guest ID guest_id
Memory (MB) memory
Image path image_path
State state
vCenter Instance UUID vcenter_uuid
vCenter Reference vcenter_ref
Network adapters nics
Base name base_name
VM namer vm_namer
BIOS UUID bios_uuid
VM Instance UUID vm_instance_uuid
Table 6. VMware vCenter Object [cmdb_ci_vcenter_object]
Field label Column name
Managed object reference ID morid
vCenter Instance UUID vcenter_uuid
vCenter Reference vcenter_ref
Table 7. VMware vCenter Datacenter [cmdb_ci_vcenter_datacenter]*
Field label Column name
Region region
Managed object reference ID morid
vCenter Instance UUID vcenter_uuid
vCenter Reference vcenter_ref
Top level folder for VMs folder_moreid
Top level folder for hosts host_morid
*The VMware vCenter Datacenter [cmdb_ci_vcenter_datacenter] table is extended from the [cmdb_ci_logical_datacenter] table, starting with the Jakarta release. In previous releases, it extended from Virtual Machine Objects [cmdb_ci_vcenter_object].
Table 8. VMware vCenter Network [cmdb_ci_vcenter_network]*
Field label Column name
Managed object reference ID morid
vCenter Instance UUID vcenter_uuid
vCenter Reference vcenter_ref
Network accessible by either hosts or virtual machines accessible
*The VMware vCenter Network [cmdb_ci_vcenter_network] table is extended from the [cmdb_ci_network] table, starting with the Jakarta release. In previous releases, it extended from Virtual Machine Objects [cmdb_ci_vcenter_object].
Table 9. VMware Distributed Virtual Switch [cmdb_ci_vcenter_dvs]
Field label Column name
VMCount vm_count
Host count host_count
Table 10. VMware vCenter Folder [cmdb_ci_vcenter_folder]
Field label Column name
Managed object reference ID morid
vCenter Instance UUID vcenter_uuid
vCenter Reference vcenter_ref
Full path fullpath
Table 11. ESX Resource Pool [cmdb_ci_esx_resource_pool]
Field label Column name
Managed object reference ID morid
vCenter Instance UUID vcenter
vCenter Reference vcenter_ref
Owner owner
Owner Managed Object Reference ID owner_morid
CPU expandable cpu_expandable
CPU limit (MHz) cpu_limit_mhz
CPU reserved (MHz) cpu_reserved_mhz
CPU shares cpu_shares
Full path fullpath
Memory expandable mem_expandable
Memory limit (MB) mem_limit_mb
Memory reserved (MB) mem_reserved_mb
Memory shares mem_shares
Table 12. VMware vCenter Datastore [cmdb_ci_vcenter_datastore]
Field label Column name
Managed object reference ID morid
vCenter Instance UUID vcenter_uuid
Accessible accessible
vCenter Reference vcenter_ref
Type type
Capacity (GB) capacity
Free space (GB) freespace
URL url
Clustered clustered
The VMware vCenter Datastore [cmdb_ci_vcenter_datastore] table is extended from the [cmdb_ci_datastore] table, starting with the Jakarta release. In previous releases, it extended from Virtual Machine Objects [cmdb_ci_vcenter_object].
Table 13. VMware vCenter Cluster [cmdb_ci_vcenter_cluster]*
Field label Column name
Managed object reference ID morid
vCenter Instance UUID vcenter_uuid
Effective hosts effectivehosts
vCenter Reference vcenter_ref
Effective CPU effectivecpu
Effective memory effectivememory
Number of effective hosts effectivehosts
Number of hosts numhosts
Total CPU totalcpu
Total memory totalmemory
Number of CPU cores numcpucores
Number of CPU threads numcputhreads
*The VMware vCenter Cluster [cmdb_ci_vcenter_cluster] table is extended from the [cmdb_ci_host_cluster] table, starting with the Jakarta release. In previous releases, it extended from Virtual Machine Objects [cmdb_ci_vcenter_object].
Table 14. VMWare Distributed Virtual Switch [cmdb_ci_vcenter_dvs]
Field label Column name
Name name
VMCount vm_count
Host count host_count
Discovery also maps the relationships to VMs and to distributed virtual port groups.
Table 15. VMware Distributed Virtual Port Group [cmdb_ci_vcenter_dv_port_group]
Field label Column name
Name name
vCenter Instance UUID vcenter_uuid
Distributed Virtual Switch Reference dvs_ref
Discovery also maps the relationship to the distributed virtual switch.
You can add these related lists to view additional discovered data:
  • Storage Volumes
    The virtual disks for this virtual machine. This data is saved in the Storage Volume [cmdb_ci_storage_volume] table with the value type=v Disk.
    Table 16. Storage Volume [cmdb_ci_storage_volume]
    Field label Column name
    Name name
    Size size
  • Network Adapters
    The virtual network adapters for the virtual disks. This data is saved in the Network Adapter [cmdb_ci_network_adapter] table.
    Table 17. Network Adapter [cmdb_ci_network_adapter]
    Field label Column name
    Name name
    IP Address ip_address
    MAC address mac_address
    Netmask netmask

vCenter relationships

Discovery automatically creates relationships for vCenter components using data from a key class. Subsequent discoveries use the same key class to automatically validate and remove relationships that are no longer valid.

vCenter CIs can be members of folders or clusters, which affect how Discovery creates their relationships.

  • If a CI is in a folder, Discovery creates a relationship between that CI and the folder. If that CI is not in a folder, Discovery creates the relationship between the CI and the datacenter. These vCenter CIs can be in a folder:
    • VM Instance
    • VM Template
    • vCenter Network
    • Datastore
    • vCenter Folder
    • vCenter Cluster
  • If an ESX server is in a cluster, Discovery creates a relationship between the ESX server and the cluster. If an ESX server is not a member of a cluster, then Discovery creates a relationship to the datacenter.
  • If a resource pool is in a cluster, Discovery creates a relationship between the resource pool and the cluster. If the resource pool is not a member of a cluster, then Discovery creates a relationship to the ESX server.