Relation and/or reference table cmdb_serial_number is not a known CI Type

[William44]

Linux discoveries fail on the Ref/Rel Linux Serial step (4.1.23 in my discovery steps). Image of step configuration is attached below.
Here are the log entries:

Mid Server agent.log entry:

12/06/18 12:41:02 (011) Worker-Interactive:HorizontalDiscoveryProbe SEVERE *** ERROR *** (104)MergeTableReferenceAndRelationClosure - Relation and/or reference table cmdb_serial_number is not a known CI Type. Check the discovery logs for more details.

Discovery Log entry:

2018-12-06 12:41:02: Relation and/or reference table cmdb_serial_number is not a known CI Type. Check the discovery logs for more details.

2018-12-06 09:41:22: Identification Engine: Discovery status is FAILURE, unable to get error message.

I have the an identical step in the windows discovery which completes without issue. An image of the windows step configuration is also attached.

So far I have attempted the following to resolve the failure:

1. I rekeyed the MID server based on recommendations and some success indicated in this ServiceNow community thread.
2. Based on the windows server discovery steps, I added a step in the Linux server discovery to insert the serial number to the CMDB_ci_Linux_Server table

Both attempted resolutions result in the same errors from the discovery and MID server logs posted above.

Any suggestions would be greatly appreciated.

[ggiri1]

Hi William,

Which version your instance is on?

- Based on error it looks like the CMDB identifier and its related entries issue.

- In general for Linux Server we do not have dedicated identifier. So it will rrely on CI Hardware identifier.

https://instance_name.service-now.com/nav_to.do?uri=cmdb_identifier.do?sys_id=a1d19344c3b33100d8d4bea192d3aedc

- Check if this has been modified (Like identifier and related items identifier entries, related entries).

- If they are modified, revert them to OOB.

- If not, check if there is any custom rule introduced in identifier entries. You can check below URL:

https://instance_name.service-now.com/cmdb_identifier_list.do?sysparm_query=applies_toLIKElinux

- If you have custom deactivate them and test.

Thanks,

Giri G

[William44]

My instance is running on Kingston.  I believe this is related to upgrades from versions prior to Geneva.  I will look into the identifier modifications.

 I don't see any deviations from OOB configurations on the CI Hardware Identifier, and there are no custom identifier entries for Linux.

Thanks for the suggestions. 

[arordeep]

Did we get a solution for this?  In our instance, we are trying to use an independent Identifier rather that using the Hardware one.  With Hardware one, it works fine but the requirement is to have a separate rule for Linux Servers.  Any help on this please?

[DuaneNMore]

I just recently had the same problem arise. I have a ticket open with SN; however they have been a bit unresponsive lately.