A server is retired from CMDB but after discovery the server status again changed to operational .

[Ankitha4]

A server is retired from CMDB but after discovery the server status again changed to operational .what might be the reason for that 

[Dr Atul G- LNG]

Hi @Ankitha4 

Might be helpful:

https://www.servicenow.com/community/cmdb-forum/cmdb-ire-engine-ignore-retired-cis/m-p/2643281

@AJ-TechTrek 

[arjun19]

Hi , please check most recent discovery of the server and there is CMDB Health staleness rule also cause if the configuration item is not discovered for certain days, then ci will move into retired state.

Thanks

[Sohail Khilji]

Hi @Ankitha4 ,

The Server retried may be operation to business and discovery may be discovering the IP via discovery schedules or other sources. You need to actually check if the CI is actually retired to the business. I hope that why your mid server is able to reach to the server and update the CI and updates its states in cmdb record. 

i hope this helps...

[AJ-TechTrek]

Hi @Ankitha4 ,

Use the CI Deletion statergy to update the status of CI.

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/conc...

https://docs.servicenow.com/ko-KR/bundle/sandiego-customer-service-management/page/product/discovery...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024