Facing issue related to most recent discovery for MCS Server in ServiceNow

Sounderrajan K
Tera Contributor

Currently in ServcieNow we are receiving MCS servers from AWS but it should be decommission in ServiceNow. Since the server removed from AWS, still the server is discoverable in CMDB. We received confirmation from AWS team that the server is no longer in AWS environment. When we troubleshoot the server by using quick discovery, we are getting the logs like "Server IP is not a reachable host (no response to target ports scanned by MID)".Kindly help us to debug and fix this issue.

1 REPLY 1

JobyV
Giga Guru

If you are talking about the Operational Status of the CIs, it is not a discoverable field. You might need to configure some staleness rules to auto retire CIs that are no longer discoverable.