The CreatorCon Call for Content is officially open! Get started here.

Discovery Help !!

SandeepKSingh
Kilo Sage

Every time when I run Discovery , multiple records of the same server appear in cmdb_ci_computer.
How to trouble shoot?

3 ACCEPTED SOLUTIONS

Ravi Gaurav
Giga Sage
Giga Sage

Hi @SandeepKSingh ,

 

Possible Root Causes & Solution:

  1. Identification Rule mismatch:
    The class’s Identification Rule doesn’t include a unique attribute like serial_number or bios_uuid.
    Fix: Go to CI Class Manager → Identification Rule → add strong identifiers (serial_number, uuid, fqdn).

  2. MID Server or IP changes:
    The server’s IP changes and Discovery uses IP for identification.
    Fix: Adjust Identification Rule to exclude IP as an identifier if DHCP is used.

  3. Discovery Pattern mismatch:
    Multiple patterns insert the same CI type (e.g., Linux and Unix patterns both run).
    Fix: Merge or prioritize patterns correctly in Discovery Pattern Editor.

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

ï”— YouTube: https://www.youtube.com/@learnservicenowwithravi
ï”— LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

View solution in original post

Dr Atul G- LNG
Tera Patron
Tera Patron

Hii @SandeepKSingh 

 

https://www.servicenow.com/community/itsm-forum/duplication-of-ci-s/td-p/714027

Duplicate server records in the CMDB occur because the Identification and Reconciliation Engine (IRE) creates a new CI instead of updating an existing one, often due to incorrect or missing CI identifiers or domain separation issues. To resolve this, verify the server's identification rules in the CI Class Manager, check for duplicate or missing serial numbers, and ensure proper MID Server configuration, especially if using domain separation. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

Hi @SandeepKSingh 

 

Below Link will Help you to understand in a better fashion
https://www.servicenow.com/community/itsm-forum/duplication-of-ci-s/td-p/714027

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

ï”— YouTube: https://www.youtube.com/@learnservicenowwithravi
ï”— LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

View solution in original post

4 REPLIES 4

Ravi Gaurav
Giga Sage
Giga Sage

Hi @SandeepKSingh ,

 

Possible Root Causes & Solution:

  1. Identification Rule mismatch:
    The class’s Identification Rule doesn’t include a unique attribute like serial_number or bios_uuid.
    Fix: Go to CI Class Manager → Identification Rule → add strong identifiers (serial_number, uuid, fqdn).

  2. MID Server or IP changes:
    The server’s IP changes and Discovery uses IP for identification.
    Fix: Adjust Identification Rule to exclude IP as an identifier if DHCP is used.

  3. Discovery Pattern mismatch:
    Multiple patterns insert the same CI type (e.g., Linux and Unix patterns both run).
    Fix: Merge or prioritize patterns correctly in Discovery Pattern Editor.

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

ï”— YouTube: https://www.youtube.com/@learnservicenowwithravi
ï”— LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

Hi @SandeepKSingh 

 

Below Link will Help you to understand in a better fashion
https://www.servicenow.com/community/itsm-forum/duplication-of-ci-s/td-p/714027

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

ï”— YouTube: https://www.youtube.com/@learnservicenowwithravi
ï”— LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

Dr Atul G- LNG
Tera Patron
Tera Patron

Hii @SandeepKSingh 

 

https://www.servicenow.com/community/itsm-forum/duplication-of-ci-s/td-p/714027

Duplicate server records in the CMDB occur because the Identification and Reconciliation Engine (IRE) creates a new CI instead of updating an existing one, often due to incorrect or missing CI identifiers or domain separation issues. To resolve this, verify the server's identification rules in the CI Class Manager, check for duplicate or missing serial numbers, and ensure proper MID Server configuration, especially if using domain separation. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

SandeepKSingh
Kilo Sage

Thanks for Quick Response @Ravi Gaurav  and @Dr Atul G- LNG