- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2022 01:06 AM
How to stop discovery from updating the retired CI's. The operation team created a new machine with the same name. Now discovery is updating the retired CI not the new one.
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2022 10:41 AM
Simple as adding an Identification Inclusion rule where state is not retired on the hardware identifier. We will skip the retired CI and create a new record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2022 10:41 AM
Simple as adding an Identification Inclusion rule where state is not retired on the hardware identifier. We will skip the retired CI and create a new record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2022 01:34 AM
Yes I tried that yesterday. And it worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2022 06:12 AM
Now after creating inclusion rule. New CI got created. The infra team created a manual CI. The serial number and name was same. It should update the manually created CI but discovery created a new one. I am sharing the identification rule we have in system. Do you know the reason?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2022 07:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2022 11:33 PM