VMware vCenter Object [cmdb_ci_vcenter_object] class
Attributes, identification rule, and other important schema structures for Virtual Machine related classes.
For descriptions of common CMDB tables in a base system, see CMDB tables descriptions.
Schema description
ServiceNow® has an extensive modeling of virtual machines (VMs) environment,
with classes such as:
- VMware vCenter Cluster [cmdb_ci_vcenter_cluster]
- VMware vCenter datacenter [cmdb_ci_vcenter_datacenter]
- VMware Virtual Machine Instance [cmdb_ci_vmware_instance]
In the diagram above, the 'Discovered' virtual server is referred to as the 'Guest' (VM object). Follow the preceding diagram for any further modeling of VMWare components.
Key reference structures
The Guest has the following important key reference structures:
- An Instantiates::InstantiatedBy relationship with the cmdb_ci_vmware_instance (which is the VM instance reported by Center).
- A Virtualizes::Virtualized by relationship with ESXi Server (the hardware with the ESXi virtualization software installed).
- Guest (Discovered, VMObject) also has a HasRegistered::RegisteredOn relationship to ESXi Server.
Identification rules
- Guest operating system: Guest operating system is modeled as Server (with IsVirtual set to true) and therefore identification rules follow the rules for the Server class. In most operating systems, BIOS UUID is reported as serial number. It is essential that you follow proper VMware guidelines to ensure that BIOS UUID is not being reused. Having a cloned BIOS UUID causes issues with identification rules.
- VM Instances: IRE uses instance MosRef ID as key identifier.
- ESX Server: Server is modeled as bare metal Server (with IsVirtual set to false) and therefore applies the Server class identification rules.