Notifications

14 views

Symptoms


When running discovery, if discovery fails at identification stage, you will have entries similar to these in the identification engine log:

Error identification_engine : MULTIPLE_DEPENDENCIES Found multiple dependent relation items [{"parent":4,"child":0,"type":"Contains::Contained by"}] and [{"parent":1,"child":0,"type":"Contains::Contained by"}] in payload identification_engine 
Error identification_engine : DUPLICATE_PAYLOAD_RECORDS Found duplicate items in the payload (index 35 and 66), using className [cmdb_ci_file_system] and fields [name]. Remove duplicate items from the payload
Error identification_engine : MULTIPLE_DEPENDENCIES Found multiple dependent relation items [{"parent":4,"child":0,"type":"Contains::Contained by"}] and [{"parent":1,"child":0,"type":"Contains::Contained by"}] in payload: no thrown error

 

The discovery log for the "Windows OS - Servers" pattern will have an entry as follows:

In case the discovered CI is included CI (such as Tomcat WAR) check if there are multiple records with name 'Contains::Contained by' in cmdb_rel_type table.
Missing identifier entry for ci type : cmdb_ci_nas_file_system . Go to 'CI Identifiers' from the navigation pane and add the needed entries.
Missing identifier entry for ci type : cmdb_ci_win_cluster_node . Go to 'CI Identifiers' from the navigation pane and add the needed entries.
Missing identifier entry for ci type : cmdb_ci_win_cluster . Go to 'CI Identifiers' from the navigation pane and add the needed entries.
Missing identifier entry for ci type : cmdb_ci_win_cluster_node . Go to 'CI Identifiers' from the navigation pane and add the needed entries.
Missing identifier entry for ci type : cmdb_ci_win_cluster . Go to 'CI Identifiers' from the navigation pane and add the needed entries.
Found multiple dependent relation items [{"parent":4,"child":0,"type":"Contains::Contained by"}] and [{"parent":1,"child":0,"type":"Contains::Contained by"}] in payload

 

Cause


There could be several reasons for duplication errors but one such cause is if the same drive letter is used for both Local Drive (cmdb_ci_file_system) and Mapped Network Drive (cmdb_ci_nas_file_system). This causes identification to fail because these are thought to be duplicates due to same identifier rule being used for both.

Resolution


Its an uncommon scenario to have the same letter being mapped to local drive and mapped network drive. The only workaround this would be to create an identifier for the NAS File System table to have an identifier entry on name and NAS_hostname.  In order to do, please follow the steps below:

  1. Discovery Definition>CI identification>Identifiers. Create New
  2. Fill the following information:
    • Name:NAS File System
    • Applies to: NAS File System [cmdb_ci_nas_file_system]
  3. Under related record for Identifier Entries tab, click New with following information:
    • Search on table:NAS File System [cmdb_ci_nas_file_system]
    • Criterion Attributes:name, nas_hostname
    • Allow Null Attribute: false

 

Article Information

Last Updated:2018-11-09 15:30:56
Published:2018-11-09