- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2018 02:19 PM
we need your advice on best way to decomission main asset classes and children from CMDB. Seervicenow provides a mechanism to remove (delete) an asset (for example a server) and all it's children. what we want to do is to mark that device AND all its children as 'Retired' and 'Non-Operational', whithout removing from CMDB. we need to avoid "orphan" entries.
this is critical to CMDB data quality.
what features avaible in Servicenow have you used to accomplish this and if this is the best approvach to address this need?
Any help is veery welcome
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2018 03:30 AM
Hi Oscar,
Are you also capturing the sub state for asset and CI ?
Check this :
1. go to Asset Ci Hardware State Mapping and filter it with "asset_state=7".
2. You will see that there are sub state values defined for both Asset and CI.
3. Check if you are following the rules.
// OOB this thing should work properly, if everything looks fine but still you are facing any issue, check for any customization in your instance that might be blocking the OOB functionalities.
Regards,
Prabhash
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2018 07:05 PM
Thank you Patrick, with your and Prabhash advice I now undertand the Asset <-> relationships and how to mark them retired in any direction. The OOO functionality works as expected.
What it's still something we need to work with is how to remove from CMDB server components no longer present in the network, for example. memory cards, network adapters, disk units. etc. from Servers that have been Retired.
Is it safe to remove (delete) all CIs with Status = 100 (Absent) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2018 03:36 AM
Oscar,
As per Best Practice we never delete anything from the CMDB.
That's why the states and substates come into picture.
Now it depends on the organization what they want to do with these types of CI. You may consult a CI Manager/ PM about how they would like to go with that.
It's something that is dependent on the process that you are following during implementation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2018 01:51 PM
thank you Prabhash. we don't want to remove anything either, so we'll use the states and sub-states to makr assets and CIs correspondingly.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2018 07:10 AM
Hello Oscar,
One follow-up answer on this is that you may need to do a bit of extra work if you want to mark the state of sub CIs such as processes and other CIs that may be created if you are running discovery. There was a Knowledge lab done by Doug a few years ago where he went over some ideas of how to implement that and I would reference that if you need some extra ideas around how to mark the state of those (or in some cases even remove if it's data you aren't using anyways). Thanks.
