Disks being labeled as orphans

[David Haught]

Hello all!

trying to get the cmdb into shape, and i am currently having an issue with the CI_disk Class

as you can see below, i have over 1k in disks that are "orphan", yet when i open the CI i can clearly see its linked to a computer, which is a valid computer.

how can i adjust the rules to see that if its on a valid computer ( has a computer listed in the field) that its not an orphan? I have been tinkering with inclusion rules, and the actual orphan rules, and i cant seem to get it right!?

any assistance would be appreciated!

[Kieran Anson]

Hi David,

Have you checked in CI class manager on what orphan rule(s) you have setup for the disk class? Could you share them (if present) so we can review.

https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag... 

[David Haught]

its currently very barebones--- i have been trying a bunch of different things though-- and it doesnt seem to do much-- except bump my number up all the way to 12k for all the Disks on the cmdb

 

[Kieran Anson]

Ah gotcha,

So in your orphanStorage screenshot, there are no relationships showing. This might be filtered on the relationship formatter, but you can confirm it by going to cmdb_rel_ci and searching for relationships between the disk and a computer record

https://yourinstance.service-now.com/cmdb_rel_ci_list.do?sysparm_query=child.sys_class_name%3Dcmdb_c...

What you might find is that there is no relationships. That's because there is a difference between a CMDB relationship, and a CMDB relationship. Your disk may only be referencing it's parent computer by the 'computer' reference field. 

So your orphan rule might look like this

1. Computer is empty
2. Computer.sys_id is empty (this takes care of invalid values in the reference field
3. Nothing defined for the relationship condition 

[David Haught]

when trying to set this up as you have mentioned, i run into an error where its requiring a relationship -- see image attached---

 but your correct on there not being a relationship between the disk and its computer-- but if thats the case, then why is it being discovered and being updated?