Configuring the discovery profile
By default, the VMware ESXi computer system sensor is enabled for a Level 2 or Level 3 discovery. The sensor discovers only guest systems that are running and does not discover ESX serial number. To change this behavior create new profile and customize sensor configuration.
Configuration items correspond to VirtualCenter sensor configuration.
The following
properties can be set to true or false:
ordinalESXviaVCserialDiscovery
- It discovers a serial number by using VMware API. This is a standard way to discover the serial number, it is faster than by using CIM API, it requires fewer privileges, but is also more prone to errors.
directESXserialDiscovery
- It discovers a serial number by using CIM API. This method always discovers the serial number,
but is slower and the following requirements apply:
- The discovery user must have the
Host > CIM > CIMInteraction
privilege. - The connection between Agile Service Manager and the ESX server is required.
Important: If you run the ESX server on virtualized hardware like Cisco UCS, you must discover the serial number by using CIM API, not VMware API, because otherwise over merges might occur. - The discovery user must have the
shallowVMdiscovery
- It discovers limited data for Virtual Machine.
discoverNonRunningGuests
- It discovers not running Virtual Machines.
strictCertificateCheck
- It forces the sensor to connect to ESX servers that are secured with valid, CA signed certificates.
enableVMDiscovery
- It enables the discovery of Virtual Machines.