ServiceNow Discovery Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago - last edited 4 hours ago
Linux server is being incorrectly classified as an Out-of-Band (OOB) device. What could be the possible causes and help me to resolve the issue. I have verified the audit history for the servers which were affected and could see for the same server's name there are 2 records created and the field "IP Address" value is changing continously, Class is flipping from "Linux server" to "OutofBandDevice".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
What to Check
- Review Identification Simulation for the affected CI.
- Check Identification Rules for both:
- cmdb_ci_linux_server
- OOB/network device classes
- Review Discovery Source and sys_object_source records.
- Check if multiple data sources are updating the same CI.
- Verify DNS forward/reverse lookups for the hostname.
- Review Discovery Logs to determine which classifier is promoting the CI to the OOB class.
✅ Issue resolved? → Mark as Correct
Found value? → Mark as Helpful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Check if multiple data sources are updating the same CI.
Yes, I could see there are 2 servers which were affected, and for those 2 servers duplicates were created with "Out-of-Band Device" class for which the source is "ServiceNow". Actual records from the class "Linux server" are coming from the source "IEDS Allmid XML"