Identification CI Errors for AIX discovery

[BK14]

Hello Community Friends,

I am getting below error when discovering an AIX server with LPAR and IBM Frames in production environment but it is successful in lower environment. The identification rules are all the same. The credentials are also testing find in Prod. I am not sure where can this happen. Please help. thank you.

Identification CI Errors:
Update failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,In payload no relations defined for dependent class [cmdb_ci_lpar_instance] that matches any containment/hosting rules: [cmdb_ci_lpar_instance >> Virtualized by >> cmdb_ci_ibm_frame]. Add appropriate relations in payload for '{"className":"cmdb_ci_lpar_instance","values":{"discovery_source":"ServiceNow","install_status":"1","correlation_id":"_","object_id":"_","sys_class_name":"cmdb_ci_lpar_instance"},"internal_id":"e20c90c561d4301054ab4fc5dc35b206","sys_object_source_info":{"source_name":"ServiceNow"},"settings":{},"sys_ire_info":{"ire_received_time":"2021-05-21 14:24:03"}}',Too many other errors,Insertion failed with error: commit failed or was not attempted due to other errors.
Identification Relation Errors:
Too many other errors

[Alikutty A]

A resolution for this issue is specified in the following support article. Create the relations as mentioned and should be resolving it

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0725816

[BK14]

Thank you Alikutty,

In the link you sent it is asking to go to Dependent Relationship in the Class Manager for that CI class but I don't even see that menu there. Is there a property that I should turn on or off to see that option in Class Manager?

Thank you

bk

[BK14]

Sorry Alikutty but I was checking under AIX server in Class Manager but I should've checked the IBM LPAR Instance instead.

Ok so the dependent relationships is shown below are the same in Prod and non prod instances so I think this is not the issue. We currently also do discover the some AIX servers and their related LPARs/Frames. Only some throw this error for some reasons.

Any idea what is causing to throw that error in the payload?

[Alikutty A · Accepted solution]

Have you followed the entire resolution steps mentioned in the KB article? For your specific device, there are some extra relations scanned via discovery and the pattern is not able to deal with it. You need to follow the exact steps reviewing the output response from ECC queue and take action accordingly.