ServiceNow Discovery creating a new CI even though an existing CI has the same Name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi ServiceNow Community,
I have an issue with Discovery/IRE.
An existing CI already has the same Name as the device being discovered, but Discovery creates a new CI instead of updating the existing one.
The existing CI has no Serial Number, while Discovery retrieves a Serial Number for the device.
My Hardware Identification Rule has these active identifiers:
1. Product Instance Identifier — Priority 90
2. Name — Priority 95
3. Serial Number lookup — Priority 100
4. Serial Number — Priority 200
5. IP Address — Priority 350
6. MAC Address lookup — Priority 400
Since Name is an active identifier with Priority 95, I expected Discovery/IRE to match the existing CI based on Name.
Why is IRE creating a new CI instead of matching the existing CI by Name? Does the missing Serial Number on the existing CI prevent the Name-based match?
What IRE/Identification logs should I check to understand why the existing CI was not matched?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Share the record details ? When the first one was created and how? is it possible to share a sample here : one for existing record and one for payload which you are trying to ingest? Is it getting created in same class? can you check if any reconsilation rule been created for discovery source?
Regards,
Pratiksha