Discovery collects information about VMware resources in your cloud service accounts.
Distributed Resource Scheduler (DRS) discovery
VMware Discovery collects these DRS settings and saves them to the
DRS VM Config [cmdb_ci_drs_vm_config] table:
DRS settings of vCenter clusters.
DRS settings of VMs configured to override cluster behavior.
Tableau 1. DRS VM Config [cmdb_ci_drs_vm_config]
Field label and Name
Description
Cluster [cluster]
The vCenter cluster that the VM belongs to.
DRS behavior [drs_behavior]
The VM-level Distributed Resource Scheduler behavior that overrides cluster defaults.
DRS enabled [drs_enabled]
Indicates whether DRS is active for the VM.
Virtual machine [virtual_machine]
The VM instance using these DRS settings.
VMware tags
VMware Cloud Discovery finds VMware tags from vCenter and saves them
to the Key Value [cmdb_key_value] table.
Tableau 2. Key Values [cmdb_key_value]
Field label and Name
Description
Configuration item [configuration_item]
Referenced VM with tag attached in vCenter.
Key [key]
Category name of the tag applied to the resource in vCenter.
Tag [tag]
Source in vCenter from which tags are fetched. In this case, the value is
always Tags.
Value [value]
Tag name that's applied to the resource in vCenter.
Data collected for VMware vCenter Server
Discovery identifies and
classifies information and data about VMware vCenter servers.
The vCenter table schema is illustrated in the following diagram:
Figure 1. 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 sub tables that extend the
cloud-agnostic tables to find discovered configuration items (CIs).
Discovery uses multiple vCenter probes to
collect this data from vCenter. The data is saved in tables extend from the Configuration
item [cmdb_ci] table.
The full vCenter instance name returned by VMware.
Instance UUID [instance_uuid]
A unique identifier assigned to the vCenter instance.
URL [url]
The endpoint URL used to connect to vCenter.
Fully qualified domain name [fqdn]
The fully qualified domain name of the vCenter server.
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.
Tableau 4. DRS VM Config [cmdb_ci_drs_vm_config]
Field label and Name
Description
Cluster [cluster]
The vCenter cluster that the VM belongs to.
DRS behavior [drs_behavior]
The VM-level Distributed Resource Scheduler behavior that overrides cluster defaults.
DRS enabled [drs_enabled]
Indicates whether DRS is active for the VM.
Virtual machine [virtual_machine]
The VM instance using these DRS settings.
This table stores DRS behavior for the VMs that
override the cluster behavior. For more information on DRS, see VMware's documentation on
Distributed Resource Scheduler.
Tableau 5. VMware vCenter VM Group [cmdb_ci_vcenter_vm_group]
Field label and Name
Description
Cluster [cluster]
The cluster that this VM group is associated with.
The VMware vCenter VM group [cmdb_ci_vcenter_vm_group] table has Contains::Contained by
relationship with cmdb_ci_vmware_instance. This group has a set of VMs.
Tableau 6. VMware vCenter Host Group [cmdb_ci_vcenter_host_group]
Field label and Name
Description
Cluster [cluster]
The cluster that this host group belongs to.
The VMware vCenter Host Group [cmdb_ci_vcenter_host_group] table has Contains::Contained by
relationship with cmdb_ci_vmware_instance. This group has a set of hosts.
*The VMware vCenter Cluster [cmdb_ci_vcenter_cluster] table is extended from the
[cmdb_ci_host_cluster] table.
Tableau 19. Cluster VM Host Rule Info [cmdb_ci_cluster_vm_host_rule]
Field label and Name
Description
VM Group [vm_group]
VM group to which the rule applies.
Host Group [host_group]
Host group associated with the rule.
Mandatory [mandatory]
Indicates whether the rule must be strictly enforced.
Affinity [affinity]
Whether VMs must run together or be separated.
Tableau 20. Cluster VM Affinity Rule Info [cmdb_ci_cluster_vm_affinity_rule]
Field label and Name
Description
Affinity [affinity]
Defines whether grouped VMs must stay together.
The Cluster VM Affinity Rule Info [cmdb_ci_cluster_vm_affinity_rule] table has
Contains::Contained by relationship with cmdb_ci_vmware_instance. This group has a set
of VMs for which this affinity is applied.
The license key to which this usage record applies.
Software Install [software_install]
The installation record tied to the consumed license.
Used By [used_by]
The asset or component consuming the license.
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 isn’t 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 isn’t 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 isn’t a
member of a cluster, then Discovery creates a relationship to the
ESX server.
This diagram illustrates vCenter relationships:Figure 2. vCenter relationships
Parent class
Relationship type
Child class
Computer [cmdb_ci_computer]
Virtualized by::Virtualizes
ESX Server [cmdb_ci_esx_server]
Remarque :
The relationship created from
ESX Server and VM Instance to the Guest are created by business rule
"Virtual Computer Check." The guest machine must be discovered after
the VCenter is discovered to trigger the business rule and create such
relationships.
Computer [cmdb_ci_computer]
Instantiates::Instantiated by
VM Instance [cmdb_ci_vmware_instance]
Remarque :
The relationship created
from ESX Server and VM Instance to the Guest are created by business
rule "Virtual Computer Check." The guest machine must be discovered
after the VCenter is discovered to trigger the business rule and
create such relationships.
These additional relationships are created when Cloud Management (CMP) is active.
Parent class
Relationship type
Child class
ESX Server [cmdb_ci_esx_server]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
vCenter Folder [cmdb_ci_vcenter folder]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Hosted on::Hosts
Cloud Service Account [cmdb_ci_cloud_service_account]
vCenter Cluster [cmdb_ci_vcenter_cluster]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Resource Pools [cmdb_ci_esx_resource_pool]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
VM Instance [cmdb_ci_vmware_instance]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
VM Template [cmdb_ci_vmware_template]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
vCenter Network [cmdb_ci_vcenter_network]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Distributed Virtual Switch [cmdb_ci_vcenter_dvs]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Distributed Virtual Port Group [cmdb_ci_vcenter_dv_port_group]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Datastore [cmdb_ci_vcenter_datastore]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Virtual Disk [cmdb_ci_storage_volume]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
Virtual NIC [cmdb_ci_vmware_nic]
Hosted on::Hosts
vCenter Datacenter [cmdb_ci_vcenter_datacenter]
VM Template [cmdb_ci_vmware_template]
Use End Point To::Use End Point From
Block Endpoint [cmdb_ci_endpoint_block]
VM Instance cmdb_ci_vmware_instance
Use End Point To::Use End Point From
Block Endpoint [cmdb_ci_endpoint_block]
Virtual Disk [cmdb_ci_storage_volume]
Implement End Point To::Implement End Point From
Block Endpoint [cmdb_ci_endpoint_block]
Virtual NIC [cmdb_ci_vmware_nic]
Implement End Point To::Implement End Point From
NIC Endpoint [cmdb_ci_endpoint_nic]
VM Template [cmdb_ci_vmware_template]
Use End Point To::Use End Point From
NIC Endpoint [cmdb_ci_endpoint_nic]
VM Instance [cmdb_ci_vmware_instance]
Use End Point To::Use End Point From
NIC Endpoint [cmdb_ci_endpoint_nic]
VMware tags
You can attach tags to vSphere objects, such as virtual machines, through the vSphere
interface. The tags can then be grouped into categories. Objects with tags are sortable
and searchable based on the parameters that you give the tags and categories. The VMWare — vCenter VM Tags probe
discovers these tags. You can view the discovered tags by opening the virtual machine
record in cmdb_ci_vmware_instance. Then go to the Key
Values tab.
Tableau 27. Key Values [cmdb_key_value]
Field label and Name
Description
Configuration item [configuration_item]
Referenced VM with tag attached in vCenter.
Key [key]
Category name of the tag applied to the resource in vCenter.
Tag [tag]
Source in vCenter from which tags are fetched. In this case, the
value is Tags.
Value [value]
Tag name that's applied to the resource in vCenter.
Datastore data collected by Discovery
Discovery identifies each datastore in the system and creates the relationships with
the virtual machines and the ESX servers that use these datastores. Discovery uses the VMWare - vCenter Datastores probe to collect this data.
A datastore is a collection of one or more physical disks, such as an iSCSI disk, and
can be used by more than one ESXi host. However, a physical disk can only connect to one
datastore. Because ESXi hosts can share datastores, it's easy to move virtual machines
between hosts that have a common datastore.
Remarque :
From the perspective of a virtual
machine attached to a datastore, storage is provided by a single disk.
The advantages to connecting a datastore to multiple disks are:
The ability to mirror the disks for failover protection.
The ease of adding storage to the datastore.
For information about the tables used by Discovery to store data for physical disks and
their relationship to datastores and ESXi hosts, see, ESXi server discovery.
In this example configuration, two ESXi hosts share a common datastore that uses different
types of storage.
Figure 3. Datastore Discovery with different storage types
Relationships
ServiceNow provides tables that contain the relationships between an ESXi host and its
datastore and the specific disks to which the datastore is connected.
ServiceNow Discovery establishes the relationships between a
datastore, the disks attached to the datastore, and the ESXi server that hosts the
virtual machines using that datastore. From the perspective of the ESXi host, iSCSI and
fibre channel disks connected to the datastore are treated as physical disks. Discovery
doesn’t show the direct relationship of the storage disks to the ESXi host.
Remarque :
Storage can be hosted on computers that aren’t discovered by Discovery. ESXi hosts are
discovered through vCenter, and storage is discovered separately through CIM. The
system can only establish the relationship between the two when storage is discovered
before ESXi.
Tableau 28. Datastore tables
Table
Description
cmdb_ci_vcenter_datastore_disk
Stores the relationship of the physical disk to the datastore.
vcenter_datastore_hostmount
Stores the relationship between the datastore and the ESXi server to
which it’s connected.
cmdb_ci_disk
Contains the physical disks connected directly to the datastore. This table also
contains a reference to the ESXi host.
cmdb_ci_fc_disk
Contains the fibre channel disks in a storage area network (SAN) connected to the
datastore. This table also contains a reference to the ESXi host.
cmdb_ci_iscsi_disk
Contains the iSCSI disks in an IP network connected to the datastore. This table also
contains a reference to the ESXi host.
VM Instance state and status fields
These tables represent the state and status of the cmdb_ci_vm_instance in various flows such
as vCenter Discovery and vCenter Events and the business rules which
are triggered.
Tableau 29. vCenter Discovery that change various states and status fields related to Virtual Machine Instance
Source
Script or Event name
Field name
VM previous state
VM new state
vCenter Discovery
VCenterVMsSensor
Install Status
Retired
Installed
vCenter Discovery
VCenterDatacentersSensor
Install Status
State
Operational Status
Installed
Retired
Terminated
Non-operational
Tableau 30. vCenter Events that change various states and status fields related to Virtual Machine Instance
Tableau 31. Business rules that change various states and status fields related to Virtual Machine Instance and related Server
Business rule
Field name
Plugin name
Cascade operational status to VM Instance
Operational status
Pattern designer
Sync ops status for CMDB CI
Operational status
Hardware status
Install status
CMDB
ESXi server discovery
Discovery identifies and classifies information about ESXi servers and ESXi
resource pools through the discovery of vCenter and not from the direct discovery of any ESXi
servers.
Important :
ESXi server discovery is done through vCenter. Don’t specify the IP address
of the ESXi server in a Discovery Schedule. Instead, discover the vCenter through the
Discovery Schedule.
Required Roles
Users with the itil and asset roles can access
ESXii and ESXi configuration item (CI) records. To run discovery on vCenter servers, users
must have the discovery_admin role.
Credentials
To run a complete Discovery of vCenter/ESXi servers, you need vCenter credentials. If
the vmapp port probe is turned off, you must use Windows credentials to access the
Windows host on which the vCenter server runs.
Remarque :
Make sure to select a credential
Type of VMware.
ESXi server Discovery Components
Discovery identifies ESXi servers based on the correlation ID (BIOS UUID), when the
hardware manufacturer is on a certified inclusion list. So if the manufacturer is in the
compatible manufacturers list, the correlation-id must be unique. If the manufacturer
isn’t on the certified inclusion list, we check for the Managed Object Reference ID
(MORID) and Serial Number as well. After running the vCenter classifier, Discovery
launches the VMware - vCenter datacenters probe, which launches the probes that explore
the ESXi server. For the complete list of vCenter probes, see List of Discovery probes.
Component and Name
Description
Classifier [vCenter]
Classifies standalone vCenter servers.
Probe [VMWare - vCenter ESX Hosts]
Creates records for ESXi servers and host mounts. Creates
relationships between ESXi servers and vCenter components. Triggers
probes for storage Discovery.
Probe [VMWare - vCenter ESX Hosts Storage]
Creates records for ESXi host hardware: network adapters, disks,
HBAs, FC ports, iSCSI, and FC disks. Creates relationships between
DAS/iSCSI/FC disks and datastore disks.
Data collected
Basic server data from ESXi
hosts is collected by the VMware - vCenter ESX Hosts probe.
Tableau 32. Data collected by Discovery on ESXi hosts
Field label and Name
Table Name
Description
Operating System [os]
cmdb_ci_esx_server
The OS version running on the ESXi host.
OS Version [os_version]
cmdb_ci_computer
Detailed OS build or release information.
Name [name]
cmdb_ci_esx_server
Hostname of the ESXi server.
DNS domain [dns_domain]
cmdb_ci_esx_server
Domain associated with the ESXi host.
Manufacturer [manufacturer]
cmdb_ci_computer
Hardware vendor of the ESXi host.
Serial number [serial_number]
cmdb_ci_computer
Physical server hardware serial number.
CPU type [cpu_type]
cmdb_ci_esx_server
The CPU model used by the ESXi host.
CPU speed (MHz) [cpu_speed]
cmdb_ci_esx_server
Clock speed of the processors.
CPU count [cpu_count]
cmdb_ci_esx_server
Number of physical CPUs.
CPU core count [cpu_core_count]
cmdb_ci_computer
Total number of cores across all CPUs.
CPU manufacturer [cpu_manufacturer]
cmdb_ci_esx_server
Vendor of the CPU hardware.
Model ID [model_id]
cmdb_ci_computer
Hardware model identifier.
RAM (MB) [ram]
cmdb_ci_esx_server
Total physical memory installed.
Disk space (GB) [disk_space]
cmdb_ci_esx_server
Total disk capacity available.
Type [type]
cmdb_ci_disk
Type of disk.
Model ID [model_id]
cmdb_ci_disk
Hardware identifier for the disk.
Disk space (GB) [disk_space]
cmdb_ci_disk
Disk capacity of the individual disk.
Name [name]
cmdb_ci_disk
Disk name as detected by ESXi.
Name [name]
cmdb_ci_network_adapter
Network adapter name.
IP address [ip_address]
cmdb_ci_network_adapter
IP assigned to the NIC.
MAC address [mac_address]
cmdb_ci_network_adapter
Hardware address of the NIC.
Netmask [netmask]
cmdb_ci_network_adapter
Subnet mask of the NIC.
Managed object reference ID [morid]
Visualization Server [cmdb_ci_virtualization_server]
Managed Object Reference ID.
Serial Number [serial_number]
Serial Number [cmdb_serial_number]
Serial number record for CMDB correlation.
Relationships
Discovery collects the following relationship data for ESXi servers.
Base Class
Relationship
Dependent Class
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
Defines resources for:Gets resources from
ESXi Server [cmdb_ci_esx_server]
VM Instance [cmdb_ci_vmware_instance]
Registered on:Has registered
ESXi Server [cmdb_ci_esx_server]
ESXi Server [cmdb_ci_esx_server]
Provides storage for:Stored on
VM Template [cmdb_ci_vmware_template]
ESXi Server [cmdb_ci_esx_server]
Provided by:Provides
Networks [cmdb_ci_vcenter_network]
ESXi Server [cmdb_ci_esx_server]
Members of:Members
Cluster [cmdb_ci_vcenter_cluster]
ESXi Server [cmdb_ci_esx_server]
Contains:Contained by
Datacenter [cmdb_ci_vcenter_datacenter]
ESXi resource pools
Resource pools are
configured in vCenter and define the maximum amount of resources that virtual machines
using that pool can consume. If the ESXi server has additional resources to spare, an
ESXi server property enables resource pools to expand. The Name
and Owner fields of each resource pool on the ESXi server must be
configured within the ServiceNow AI Platform
in the ESXi Resource Pool
[cmdb_ci_esx_resource_pool] table. When Orchestration for VMware executes its manual
provisioning tasks, the provisioner must select the proper resource pool for the virtual
server requested. Discovery finds resource pools on ESXi machines and populates the fields
on the ESXi Resource Pool form automatically. For more information, see Configure ESXi resource pools.
ESXi resource pools require the Orchestration
- VMware Support plugin.
Remarque :
Confirm that vCenter and the ESXi server have been fully configured, including the
creation of the templates and resource pools.
Tableau 33. Data collected
Field label and Name
Table
Source
Description
CPU expandable [cpu_expendable]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Whether the resource pool can exceed CPU allocation limits.
CPU limit (MHz) [cpu_limit_mhz]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Maximum CPU allocation.
CPU reserved (MHz) [cpu_reserved_mhz]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
CPU guaranteed to the pool.
CPU shares [cpu_shares]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
CPU priority weight.
Full path [fullpath]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
vCenter folder path.
Memory expandable [mem_expandable]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Whether memory can exceed the configured maximum.
Memory limit (MB) [mem_limit_mb]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Maximum memory.
Memory reserved (MB) [mem_reserved_mb]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Memory guaranteed to the pool.
Memory shares [mem_shares]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Memory scheduling weight.
Owner [owner]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
Host or VM owning the pool.
Owner Managed Object Reference ID [owner_morid]
ESXi Resource Pool [cmdb_ci_esx_resource_pool]
VMWare - vCenter Clusters probe
VMware reference ID of the owner.
Standalone ESXi discovery
Standalone ESXi discovery supports discovery of individual ESXi servers that host
virtual machines (VMs) and related components without a vCenter. Various CIs and relationships
are discovered as part of a discovery schedule.
Required roles:
Users with the itil and asset roles can
access ESXi configuration item (CI) records. To run a standalone ESXi discovery, users must
have the discovery_admin role.
VMware credentials
To run a standalone ESXi discovery, you need VMware credentials. Create the credentials by
navigating to Discovery > Credentials > VMware Credentials.
If you use a domain account to access the ESXi host, specify the domain with the user name
in the credential record in one of the supported formats, such as
Domain\UserName.
Remarque :
The VMware credentials must have a read-only role in the ESXi host.
Requirements
Make sure the Discovery (com.snc.discovery) plugin is installed and
activated and that you have upgraded to Australia or later.
Activate the ESXi trigger probe. Navigate to the Trigger Probe [trigger_probe_m2m]
table. The esxi record is inactive by default. Mark Active as true to enable Standalone
ESXi discovery.
Create a new Discovery schedule for the host with the appropriate IP
address of the ESXi host.
Remarque :
If both SSH and ESXi are triggered, SSH is launched first and may cause Discovery
to complete with the message "ESX Discovery is only supported through the vCenter."
In this case, open the UNIX - Classify probe and set ESX - OS inactive.
ESXi server Discovery Components
Discovery identifies ESXi servers based on the correlation ID (BIOS UUID), when the
hardware manufacturer is on a certified inclusion list. If the manufacturer is on the
list, the correlation ID must be unique. If the manufacturer isn’t on the certified
inclusion list, the Managed Object Reference ID (MORID) and Serial Number are checked as
well.
After Shazzam runs, it checks for the port probe esxi. Discovery then launches the VMWare -
Standalone ESXi Server probe, which then launches the probes that explore the ESXi server.
Other existing Discovery probes are also launched. For the complete list of probes, see
List of Discovery probes.
Tableau 34. ESXi server Discovery Components
Component and Name
Description
IP Service [ESXi]
IP Service ESXi - VMWare VM console is defined for the Port 902.
Port Probe [esxi]
ESXi Server Appliance web user interface. It’s triggered by the IP
Service ESXi and it triggers the probe VMWare - Standalone ESXi
Server.
Probe [VMWare - Standalone ESXi Server]
Probe to get information about an ESXi server.
Probe [VMWare - vCenter ESX Hosts]
Creates records for ESXi servers and host mounts. Triggers other probes.
VMware - vCenter ESX Hosts Storage
VMware - vCenter Datastores
VMware - vCenter Networks
VMware -vCenter VMs
Probe [VMWare - vCenter ESX Hosts Storage]
Creates records for ESXi host hardware: network adapters, disks, HBAs,
FC ports, iSCSI, and FC disks. Creates relationships between DAS/iSCSI/FC
disks and datastore disks.
Basic server data from ESXi hosts is collected by the VMware - vCenter ESX Hosts probe.
ESXi Standalone server data
Discovery uses multiple existing probes to collect this data from ESXi. The data is
saved in various tables. Some of the CIs, which have the "server" field have a reference
to ESXi Host (for example, cmdb_ci_esx_server).
Standalone ESXi discovery also fetches the resource pools on the host including the root
resource pool. This root resource pool is hidden for every ESXi host. The root resource
pool may not be visible in the VSphere web client for the ESXi host, but you can view it
using the mob browser.
Navigate to this URL: <domain name/or
ip_address>/mob/?moid=ha-root-pool
The root resource pool groups the resources of that host. Other child resource pools can
also be created from the root resource pool. The root is identified in the ESXi host with
the Managed Object ID: ha-root-pool.
Forward migration
If you were using standalone ESXi discovery and now the same ESXi is part of vCenter, you
can use vCenter discovery instead. Create a vCenter discovery schedule and trigger it.
Triggering a vCenter discovery creates duplicate CIs in the following tables as the
identifiers for the CIs are different when ESXi is standalone or part of vCenter:
To avoid duplicates, you must mark the CIs created by standalone ESXi discovery in
the above four tables as retired. When vCenter discovery is triggered, the
vCenterESXHostsSensor script include checks for all the ESXi servers whether they were
previously discovered as standalone ESXi server. If yes, it automatically triggers the
ESXMigrationUtil script to mark all the previously discovered duplicate CIs as
retired.
Remarque :
If you want to trigger migration manually, you can do so by executing
the following script from the background script: // @params esx_sys_ids – array of
sys ids of all the ESXi servers that must be migrated.
Once an ESXi server is migrated to vCenter, triggering a standalone ESXi discovery
schedule on the same ESXi host results in an error. Discovery is aborted with an error
message that “This ESXi is part of vCenter <IP_address of Vcenter> discovery
schedule. Aborting discovery”.
