Discovery of CIs marked as "Retired" or "Non-Operational"

[ditu]

We marked some of our CIs as retired  for a test:

Status- Retired

Operational Status- Non-Operational 

These CIs are still on network and we wanted to check the impact of discovery on these records. 

Now, the these are being discovered but these are updating the same CI (that's fine). But the Status and Operational status are still the same which gives a wrong impression. 

What should be done?

[ditu]

Any ideas around it?

[robertgeen]

Your question is really a process question. Out of the box that status will not get updated when discovery discovers it. You would need to implement a business rule which sets it to a specific value on update by the mid servers if it's in that state. This should be easy enough to do and you might want to set it to a state that can easily be flagged to be looked at.

[Kiran7]

Hi Ditu,

As per my understanding in discovery whether you have marked CI as retired or Non-operational if those CI's are still present in network and configured in network whenever discovery will run they will be discovered and updated in CMDB.

And if you want to test your above mentioned scenario, you may have to temporary remove those CI's which you have marked as retired from your network.

Regards,

Kiran Salunkhe

[Rakesh16i]

If I understood correctly you are expecting that discovery will change the status from retired or Non-operational to Installed or Operational.

if yes, then please be aware that discovery will not change these values by itself. These are intended to be governed within Change Management Process.

Regards,

Rakesh Imandi