CI Identification and Reconciliation Rules Review
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi Team,
I have a request to complete
As a CMDB Administrator, i want all existing CI identification and reconciliation rules reviewed in ServiceNow, so that the current state of IRE rules is understood and gaps of misconfiguration causing duplicate CI creations are identified
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
39m ago
Hi @Rajesh77,
I wrote an article about that topic, that might help you with your task.
Identification Simulation: Testing IRE Rules and Creating Mock Data
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
26m ago
@Rajesh77 We suggest reviewing all existing CI identification and reconciliation rules in the CMDB for class which is causing duplicate CI creation.
Search for "Identification and Reconciliation Rules" in the application navigator.Open each rule to review its configuration, including:
Identification Rules: Define how CIs are uniquely identified.
- Check if the identification rules are properly configured for each CI class.
- Ensure that key attributes (e.g., serial number, hostname, IP address) are correctly defined for unique identification.
- Look for any overlapping or conflicting rules.
and Reconciliation Rules: Define which data sources have authority over specific attributes of a CI.
- Verify that reconciliation rules are aligned with the authoritative data sources for each CI class.
- Ensure there are no gaps or misconfigurations that could lead to duplicate data updates.
Finally, Check for Duplicate CIs:
- Use the Duplicate CIs module or run a query to identify existing duplicates in the CMDB.
- Analyze the root cause of duplicate creation (e.g., missing or incorrect identification rules).