Discovery CMDB identifiers

The CMDB identifiers provide a single point of entry for inserting and updating CIs in the CMDB that ensures data integrity.

These identifiers simplify the way applications such as Discovery, ServiceWatch, and SCCM interact with the CMDB. By providing a common interface for updates, the system reduces the probability of duplicate CIs from the different sources. Both probes and sensors use identifiers.

Identifier tables

Table 1. CMDB identifier tables
Table Description
Identifier [cmdb_identifier] Stores all identifier rules.
Identifier Entry [cmdb_identifier_entry] Stores all the identifier attributes.

Default identifiers

The default Discovery system contains the identifiers below, each of which is associated with a specific CI type (the sys_class_name field on the CI record) or the table in the Applies to field and contains the appropriate attributes for discovering CIs from the specified table. Where necessary to discover all possible occurrences of an attribute, tables from related lists (Search on tables) are included in the rule. For more information, see Create or edit a CI identification rule.

Table 2. CMDB identifier rules
Rule Applies to table/attributes Search on table/attributes
ESX Server Rule ESX Server [cmdb_ci_esx_server]
  • correlation_id
none
Hardware Rule Hardware [cmdb_ci_hardware]
  • serial_number
  • serial_number_type
  • name
  • ip_address
  • mac_address
  • Serial Number [cmdb_serial_number]
    • serial_number
    • serial_number_type
  • Network Adapter [cmdb_ci_network_adapter]
    • ip_address
    • mac_address
Storage Server Rule Storage Server [cmdb_ci_storage_server]
  • cim_object_path
  • name
  • serial_number
  • serial_number_type
  • mac_address
  • ip_address
  • Serial Number [cmdb_serial_number]
    • serial_number
    • serial_number_type
  • Network Adapter [cmdb_ci_network_adapter]
    • ip_address
    • mac_address
WBEM Service Rule WBEM Service [cmdb_ci_wbem_service]
  • cim_object_path
none

Matching strategy for the hardware identifier

In the Helsinki release, the sys_class_name cannot be an attribute for independent rules, such as cmdb_ci_hardware. If your Discovery identification strategy depends on matching a CI with a specific class, you must create a new rule for each class you want to use for matching and specify that class in the Applies to field of the Identifier form.

For example, you can create an identifier for a Linux server with different attributes than the Hardware Rule. You might only want to use the machine name, IP address, and MAC address for identification. Your new rule would look like this:
Figure 1. Linux identifier
Linux identifier rule

Selecting identifier versions

All new instances use identifiers from the CMDB Identification and Reconciliation framework. Upgrades from pre-Geneva versions still preserve the legacy identifiers, but you can switch to the new identifiers using a property: glide.discovery.use_cmdb_identifiers. If you upgraded from a pre-Geneva version, you must manually add this property and set it to true to use the new identifiers. If you upgraded from Geneva or later releases, this property is available in the System Properties [sys_properties] table. To preserve functionality in custom legacy identifiers, convert them to the new CMDB identifier rules format before enabling this property. The system does not reconfigure your custom identifiers to the new framework automatically.
Note: When Service Mapping is active, the new identifiers from the CMDB Identification and Reconciliation framework are always used regardless of the property value.