Discovery can explore the VMware vCenter process running on a Windows or Linux host. IPv6 is supported for VCenter.

Note:

If a Windows or Linux server is running vCenter application, after creating the vCenter CI, a "Runs on" relationship to the Windows or Linux server host is created.

When a vCenter application is running on a dedicated vCenter appliance, "Runs on" relationship to the vCenter CI is not created.

Tested vCenter versions

The ServiceNow® platform supports vCenter API versions 4.0 and higher. The following versions were tested with the Xanadu release:
  • vCenter versions 7.0 and earlier
  • vCenter appliance version 6.7 and earlier
For installations based on the vCenter appliance, a server CI is created for vCenter appliance and the following fields are populated:
  • NameIP
  • AddressMAC
  • AddressDiscovery
  • Source
Note: If you are discovering SUSE Linux hosts for vCenter appliances, version 6.0 and earlier, observe these SSH restrictions.

See Data collected for VMware vCenter Server for a description of the VMware architecture and component relationships.

vCenter discovery process

After classifying vCenter, Discovery launches the VMware - vCenter Datacenters probe, which in turn launches specific probes that return information about ESX machines, virtual machines, and other vCenter objects. The vmapp port probe is also configured to launch the VMware - vCenter Datacenters probe.

VMWare credentials

If you use a domain account to access vCenter, specify the domain with the user name in the credential record in one of the supported formats, such as Domain\UserName. The VMware credentials must have read-only role and License Admin privilege in vCenter.
Important: Windows credentials are not necessary for vCenter Discovery, when valid VMware credentials are used.

Updating the CMDB with vCenter event collector

In addition to finding vCenter data through the standard discovery process, Discovery can also update the CMDB by detecting vCenter events through a MID Server extension called the vCenter event collector.

The event collector allows the CMDB to be updated with changes to virtual machines (VMs), in addition to the updates detected by Discovery. A change to a VM is sent as an event from the vCenter server to the vCenter event collector. When an event is received, the CMDB is updated accordingly. Full vCenter Discovery does not need to rerun. For some events, such as powered on and powered off events, Discovery does not need to run again at all. For most events, Discovery runs only on the necessary vCenter resource.

For instructions on configuring vCenter events, see Configure and run the vCenter event collector extension.

VM deleted from vCenter

If the VM is deleted from vCenter, the cmdb_ci_vm_instance state changes to terminated and the Status field changes to retired.

CIs removed from vCenter

When a vCenter CI, such as a virtual machine, is removed, the ServiceNow instance marks it as "stale" in the CMDB, using either of these procedures:
  • When Discovery runs, it creates an audit record in the Components installed with CMDB Health table for the missing CI and marks the CI "stale".
  • If the instance is configured to collect vCenter events, the system can also create a "stale" audit record for the CI in the CMDB Health Result [cmdb_health_result] table from the VmRemovedEvent event, without having to run Discovery.
Note: When the Staleness setting is configured, the dependency view (BSM map) grays out stale CIs in its relationship diagram to indicate that they were removed from vCenter.
Figure 1. vCenter CI marked as "stale"
vCenter CI marked as "stale"

You have the option of creating a CMDB remediation rule to automatically execute a remediation workflow that can, for example, delete stale CIs. For more information on stale CIs, see CMDB Health Metrics.

vCenter Discovery on Windows host

Windows credentials are not necessary for vCenter Discovery, when valid VMware credentials are used.