Identification Relation Errors for Network Switch

Uday Gonuguntla
Giga Guru

Hello Experts,

 

Can someone please help me to understand this error? I got this under payload processing.

Identification CI Errors:
Insertion failed with error,Insertion failed with error
Identification Relation Errors:
Found multiple relations [parent:'21fa3cfadb3a9010d187c170ba96190c'/child:'ffeab8fadb3a9010d187c170ba96194d'/type:'25242fb2377a9200738d021a54990e88'] between payload items: '[{"className":"cmdb_ci_network_adapter","values":{"discovery_source":"ServiceNow","install_status":"1","netmask":"255.255.255.0","mac_address":"00:08:e3:ff:fc:28","name":"Vlan4","alias":"128","ip_address":"10.130.3.254","sys_class_name":"cmdb_ci_network_adapter"},"sys_object_source_info":{"source_name":"ServiceNow"},"settings":{},"sys_ire_info":{"ire_received_time":"2020-10-12 09:08:11"}}]' and '[{"className":"cmdb_ci_ip_address","values":{"discovery_source":"ServiceNow","ip_version":"4","install_status":"1","netmask":"255.255.255.0","ip_address":"10.130.3.254","sys_class_name":"cmdb_ci_ip_address"},"sys_object_source_info":{"source_name":"ServiceNow"},"settings":{},"sys_ire_info":{"ire_received_time":"
1 ACCEPTED SOLUTION

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @Uday Gonuguntla,

I recently came across same issue with some other customer and this happens when you have multiple relations with payload and existing CI records.

Generally the errors will be shown if any issues with the CI relations within the payload but if you check here, you see the sys id's as well in the error.

This will be because of the duplicate CIs but not sure of how you got them. You can check in your instance in the relevant CI tables with those sys ids and you can see the payload content and the existing CI content will be same.

All I would suggest is to remove the existing records related to this pattern discovery and do a fresh discovery. This should work.

 

Please mark the appropriate responses as Correct/Helpful so that this thread gets closed and helps others with the same question in the future.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

View solution in original post

9 REPLIES 9

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @Uday Gonuguntla,

I recently came across same issue with some other customer and this happens when you have multiple relations with payload and existing CI records.

Generally the errors will be shown if any issues with the CI relations within the payload but if you check here, you see the sys id's as well in the error.

This will be because of the duplicate CIs but not sure of how you got them. You can check in your instance in the relevant CI tables with those sys ids and you can see the payload content and the existing CI content will be same.

All I would suggest is to remove the existing records related to this pattern discovery and do a fresh discovery. This should work.

 

Please mark the appropriate responses as Correct/Helpful so that this thread gets closed and helps others with the same question in the future.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

Hello,

 

Thanks for your response. When I searched with that sys id available in payload, I couldn't find duplicates. Also do i need to delete all three records like parent, child and relationship type? Please suggest me.

 

Thanks,

Uday

Hi,

Please also check the cmdb_rel_ci table for this where you have a relationship for this parent and child with that type.

 

Thanks,
Ashutosh

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @SNowUser11,

Do not delete relationship type.

I meant duplicates b/w your payload and existing values in CMDB of same class. So check the actual CI table with the sys id's in the above errors.

Delete those respective existing entries in respective parent and child CI tables with the help of sys ids in the errors.You can see from error the CI name as well as sys id.

Also if possible you can delete the entries in other CIs that are discovered through network switch pattern but this is not mandatory, just to be clear.

 

Once you do this, then try fresh discovery and you will not see these IRE errors. As mentioned earlier same issue was resolved in a recent customer case.

 

Please mark the appropriate responses as Correct/Helpful so that this thread gets closed and helps others with the same question in the future.

Please mark Helpful / Accept Solution so that it helps others with similar questions.