CMDB Health Duplicate - Help!

[Henrik Jutterst]

Can someone please explain to me why a record is considered a duplicate?? Using Madrid

I have my Identification Inclusion Rule set up and prio 100 is Name (Fig. 01). And as I understand it, if the Name IS unique for a Linux server CI it shouldn't be a duplicate. But when I go through Duplicate Task table (Fig. 02) [reconcile_duplicate_task] it says that IP address is not unique - and that's true - they have the same IP-address (but that's another debate since it is wrong data).

But WHY does not identifier with prio 100 (Name) mark them as separate CIs?

As I understand it, according to these blogs/articles the identifier with highest prio should rule?!

• Getting Started: CMDB Health Automation
• Discover multiple CIs with the same serial number - Part I

Here is the Identification Inclusion Rule for Linux Server:

Fig. 01

My Duplicate Record:
Fig. 02

[vNick · Accepted solution]

Hi Henrik,

The reason you get duplicates is still because IP Address is a rule defining uniqueness.  If you disable that rule, you will not get a duplicate violation.  Even though Name is a higher priority and you match on that, when assessing duplicates ALL identification rules are assessed, which is why you get the duplicates.  ALL identification rules apply when assessing uniqueness, regardless of how something like discovery or import sets may match records.

Hope that helps

Nick 

[Henrik Jutterst]

Thank you Nick, that was just what I needed to clarify.
Much appreciated!

/Henrik