How to stop discovery from updating the retired CI's.

pratiksha5 · ‎03-31-2022

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.

doug_schulze · ‎03-31-2022

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.

View solution in original post

Rahul Priyadars · ‎03-31-2022

It not a good practice where 2 Ci with same name and 1 is retired and other is active in Same CMDB Class.

Method 1

Rename OLD CI name with some prefix

Try removing all Identification Key Attributes (Serial No, Serial No type ,)from OLD CI and run discovery.

Method 2

Take XML backup of the Old CI

Delete OLD CI

Run Discovery for New CI it will update

Export Back the OLD CI

Method 3

Delete Duplicate Name OLD CI from CMDB

Run Discovery there will be only 1 CI with that name

Regards

RP

pratiksha5 · ‎03-31-2022

Hi Rahul, Thank you for the reply. I created inclusion rule saying the status should not be retired. It did created a new CI now. I informed them about the best practice for naming the servers.

Rahul Priyadars · ‎03-31-2022

Please close the thread.

Rajendra12 · ‎03-31-2022

As far as the CI is discoverable (Patterns matched) it will be updated no matter what the state of CI is.

If the CI is retired, it should be removed, powered off so that it is not discoverable.

With this you can also conclude that it is dangerous to have two CIs with same name one in retired state and one in active state, if the pattern matching is same for both you don't know which one will be updated.

Regards

Rajendra