- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-11-2018 10:19 AM
Hello, Does discovery still update the retired CIs? Thanks!
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-11-2018 10:26 AM
Out of the box yes it will discover and update it. It's one of those weird things where is it really retired if you can discover it? The other thing is that Service Mapping is different and will actually not discover it if it's marked as operational status = retired. Either way in general you may want to setup a process for these to flag them somehow so you can follow-up on them (or even used most recent discovery date to form a process). Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-11-2018 10:58 AM
I concur with Robert. Aside from what Discovery and Service Mapping do or do not do out of the box, the more important question is what to do about it. Retiring CIs and assets is a process, and there should be several (at least two) states to indicate where you are in that process of retiring a CI. When the owner is done using it, they can suspend usage, and this should be detectable through status or some other field. Then the process of retiring the CI should include any cleanup, security and privacy protection measures, removing any configuration dependencies, powering down the system, and finally the reclaiming or disposing of the physical asset if applicable. Only then should a CI be completely retired. If you have a system that is specified as Retired but it is still powered up, this is a potential security and compliance issue, as well as a power consumption cost. If your Retired state indicates a final state of the CI, then it would be good to be able to report on any unexpected Discovery of this asset, and define CMDB Remediations or other processes to address the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-11-2018 11:07 AM
Hi All,
Out of the box Ci's will discover what ever the state they are. If You don't want to discover any CI in Retire state then you need to configure "Identification Inclusion Rules" on CMDB_CI_HARDWARE table.
Applies to# Hardware [cmdb_ci_hardware] or what ever the table you want to puta constaint.Inclusion condition# install_status!=7 Note# Number 7 represents "Retired" status.
Hope this helps...
Thanks & Regards,
Vinil Reddy. Yeruva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2021 06:36 AM
Will this remove ci from cmdb? I mean all we want is the retire ci should not come on map.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2021 05:15 PM
It will not remove the CI from the CMDB.
If a CI is marked as retired, and Discovery finds it, it will either (a) update it (OOB setting) or (b) create a new CI if you have any inclusion rules (example above)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2021 05:21 AM
Ohk we are facing an issue with retired ci coming on the service map. Trying to find a solution apart from BR or Schedule job.
