ServiceNow Discovery not discovering a CI anymore due to decommissioning

[Ed Laar]

Hi,

I am in doubt about the ServiceNow Discovery behavior as soon as a CI is decommissioned so it's not operational anymore: What will ServiceNow Discovery do in the CMDB in this use-case?

I always was under the impression that, as soon as the CI is not available on the network IP-address anymore ServiceNow Discovery would not update that CI anymore (as no up2date info is available anymore) and that a seperate process or job should check for CI's with a Last discovered date of period x ago to set these CI's into Retired_Non Operational.

Probably this has been changed. Please let me know.

Thanks in advance,

Ed  

[Niks1]

Hi Ed,

As per my knowledge goes , a decommissioned CI will not respond to port scan probe hence there is no chance for discovery to progress to identification and exploration phases to update the CI.
So to answer your query , the discovery will not update the CI , once it is decommissioned ( off network). Also the "Operational status" field is not updating via discovery response (as discovery is failing) hence the Configuration team or CI auditor should update the CI's operational status as "Retired".

Hit thumbs-up sign if my response helps you with your query.

Regards,

Nikhil (Niks)

[Niklas Peterson · Accepted solution]

Hi,

Different things can happen depending on the deletion strategy set up for the CI class.

https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/discovery/concept...

Regards,
Niklas

[Ed Laar]

Thanks Niklas, so a deletion strategy can be defined for related CI's but not for the main CI exept some occasions.

So what to do in case a main CI is not discovered for a certain period of time? Such CI's are called stale CI's isn't it? Should such CI's be checked periodically and set to Retired manually? I can also think about an automatic procedure to do this.

Looking forward to your response.

Grtz,

Ed

[Niklas Peterson]

Hi Ed,

Yes, stale CIs must be managed. For that you have the CMDB Health functionality. Staleness is part of the Correctness measurement. CMDB Health also comes with support for remediation. A remediation rule can trigger a Flow with actions for the stale CI.

https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/configuration-manageme...

Regards,
Niklas