Duplicate records are getting discover with the same name and IP address

[kambleneeta20]

Hi,

We are facing issue- after the upgrade from Istanbul to Jakarta , duplicate records are getting discover by the discovery .

It is skipping the identification rule and with the same Name and IP address few duplicate records are getting created -

Please check the below screenshot of the identification rule.

Can some one please suggest ? Thanks in advance

[kambleneeta20]

Hi Nikhil ,

I found some clue from below community article -

https://community.servicenow.com/community?id=community_blog&sys_id=3efc66a5dbd0dbc01dcaf3231f96193b

It seems due to property “glide.identification_engine.skip_duplicate =true ” it is marking discovery status as duplicate.

I want to exclude it for few CI could you please help me , I am not able to find out any business rule / or script.

Could you please help me out, thanks.

[kambleneeta20]

Hi Nikhil ,

I found some clue from below community article -

https://community.servicenow.com/community?id=community_blog&sys_id=3efc66a5dbd0dbc01dcaf3231f96193b

It seems due to property “glide.identification_engine.skip_duplicate =true ” it is marking discovery status as duplicate.

I want to exclude it for few CI could you please help me , I am not able to find out any business rule / or script.

Could you please help me out, thanks.

[Ashutosh Munot1]

HI Neeta,

Hope you are doing good.

Now can you tell me on thing, which identifier shows NO MATCH in logs?

Then also tell me the class of this CI's

Thanks,
Ashutosh

[kambleneeta20]

Hi Ashutosh,

Thanks for your reply.  Hope you are fine.

This issue is in all the identifier rule and in all the classes.

E.g.  Hardware identifier and hardware/Linux classes.

[Ashutosh Munot1]

HI Neeta,

Then we have to first work on this, put proper identification rules and Classification rules. One Serial number should have one CI , if multiple then discovery will mark them as duplicates.

Thanks,
Ashutosh