CMDB relationships: Creating the right ones when CIs have the same name

[martinrymell]

I am using Discovery to populate the majority of hardware items in the CMDB, and am looking to use Service Mapping to create relationships to Business Services in the future.   Until then the team is creating relationships manually and by loading relationship data to cmdb_rel_ci.

The challenge we face when loading relationship data is when Discovery has created CIs with the same name but different classes (e.g., a server and a virtual instance).   Loading Parent / Type / Child to cmdb_rel_ci where Parent = Business Service and Child = asset CI sometimes relates the virtual instance instead of the intended server to the Business Service.   It looks as though the transform map creates the relationship for the first CI it finds where multiple CIs have identical names, although I haven't proved that conclusively.

I've considered the solution of exporting the server CIs I want to relate to Business Services and their sys_ids to create a data load and transform map to map the sys_ids to report_parent_sys_id and report_parent_child id.   The team is going to test that, however it feels like a reactive and inelegant solution to the challenge.

Does anyone have any experience of this and any other potential solutions to share please?   Thank you.

[suchi]

Hi Scott,

Any luck?

Can you please elaborate if it solves your issue.

Thanks,

Suchi

[suchi]

Any one found any solution for this?

I am also having the same issue. In Target Table I am not able to get class field where as it is present only in source Table (u_parent_sys_class_name & u_child_sys_class_name) & hence not getting any relevant field to map with Target Table.

When schedule job runs its randomly picks the CIs with same name but not the same class we are looking from source sometimes. How to control this. Please help.

Thanks,

Suchi

[suchi]

Any solution?