Same CI in different class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2022 12:39 PM
Hi Experts,
We have discovered/integrated V-center in ServiceNow along with all topology. classes show the CI data. On other hand in horizontal discovery I do have scheduled discovery configured to scan using IP ranges. The issue am facing is all the guest OS regardless of Linux/windows OS type hosted on ESX servers as guests OS, are getting populated as "VMWARE Virtual Machine Instances" class and has relationship also correctly setup.
The issue is that my IP range based discovery also discovering same CI and creating record in other ServiceNow respective classes based on OS class such as windows /Linux/Unix.
I find that same record is added twice in two different classes and table. When we do third party integration where we need to check hostname exist or not, issue occurs as multiple CI with same name exist.
I would like to know is this normal? it seems an issue that same set of data at multiple tables and reconciliation of data did not occurred because you already have different class defined for certain integration. shouldn't the class be considered later and first it should validate where th?
Could you please advice on this if this is correct behavior?
Thanks
SS
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2022 08:36 AM
hi
is anyone looking into my request? can someone advice
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2022 08:56 PM
found another link has explanation on the same concerns but i have extended my concerns with ITOM related use case
https://www.servicenow.com/community/architect-forum/same-ci-in-different-class/m-p/2373298#M2785