Understanding why IRE isn't matching on Identification Rule

[MarkyMark1]

I'm trying to understand why the IRE doesn't believe there's a CI match when from my point of view it appears there should be.   I'm running the Identification Simulation on a simple payload.

 

If you look at the network adapter class there is indeed a matching CI with the same mac address and name.

The CI identifier shows the valid entry used to determine such a match.

Yet the Output Payload finds no match and therefore wants to instead insert a new record.   What am I missing here?  thanks!

[#2]

Here is my best guess.

The existing network adapter record in the cmdb has no Owns::Owned By relationship to a hardware CI.  It may have the reference to cmdb_ci populated, but there isn't a relationship to it.

The OOTB IRE rules on network adapter state it is dependant on Harware with an Owns::Owned By relationship (hardware is the parent).

If you have a network adapter that exists in the CMDB without this relationship it is orphaned.  When you send the payload over even if name and mac address are matches, it will not be matched by the IRE as the dependant relationship doesn't exist.

[MarkyMark1]

Makes sense and I can verify that the network adapter class is setup with owns::owned by betweeo it and the hardware class.  Would you elaborate on how exactly I could verify if this specific network adapter record doesn't have a relationship to the hardware CI?

[#4 · Accepted solution]

You will need to check cmdb_rel_ci.

The dependent relationship is defined as such:

Showing hardware as the parent, Owns::Owned By as the relationship type, and network adapter as the child.

The best way would be to go to cmdb_rel_ci.list to view relationships.  Add a filter where 'Type' is 'Owns::Owned By' and 'Child' is your network adapter's name.

If there is not a relationship in that query where the parent is your ROF... linux server then the relationship doesn't exist.

[MarkyMark1]

That was exactly the missing piece.  The examples I was focused on they both did not have a relationship defined in the cmdb_rel_ci table to meet the dependency requirement of requiring the network adapter have a hardware ci.   I wish the logging pointed that out to me more clearly but now at least I know what else to look for.

Thanks