Discovery of device fails with error "Relation and/or reference table is not a known CI Type"
Discovery of the device fails with error "Relation and/or reference table is not a known CI Type"
Cause
Pattern step of operation type "Create Relation/Reference" creates a relationship between two tables. However, the parent table is not present on the "Related Entries" of the child table identifier.
For example, the "Network Switch" pattern may create a relationship between discovery_net_arp_table and the cmdb_ci_ip_switch. When using the OOB "Hardware Rule" this works as expected as related entries have an entry for discovery_net_arp_table. However, a user may create a new identifier higher up in the hierarchy which will now be used by the cmdb_ci_ip_switch. If such an identifier does not contain a "Related Entry" for the discovery_net_arp_table table, then the error would be seen. In this case, the error would be "Identification Engine: Discovery status is FAILURE, Identification sections in pattern failed: section: discovery, error: Relation and/or reference table discovery_net_arp_table is not a known CI Type."
Resolution
- Determine the identifier being used for the table, review the "Create Relation/Reference" step and find the "Child" table.
- Navigate to the identifier and add the "Parent" table to its "Related Entries", the one listed in the error message (discovery_net_arp_table table in the example listed in the "Cause" section of this KB).
- Run discovery of the device again and confirm the issue is resolved.
Note: To find the identifier used, search the cmdb_identifier table for records where "Applies to" matches the "Child" table. If none is found, search for the table which the "Child" table is extended from and so forth.
https://www.servicenow.com/community/itom-articles/discovery-of-device-fails-with-error-quot-relation-and-or/ta-p/2295779