Servers constantly changing state in CMDB from operational to non-operational and back.

Marco Jansen
Tera Contributor

3 weeks ago

We see behaviour in servers states in the CMDB where the state is constantly changing from operational to non-operational and back. We rely on this state for our automated patching so unexpected state changes is not what we want. Is anyone else in the community seeing this as well and did you managed to solve it? If so please guide us how, if not, then we ask servicenow what this could trigger and how we need to solve this?

 

See the attached screenshot. In Azure the servers are in running state, while the CMDB sees them as non-operational? 

Preview file
203 KB
0 Helpfuls
  • 490 Views
1 REPLY 1

vaishali231
Mega Sage

2 weeks ago

Hey @Marco Jansen 

I would suggest checking the CI audit history to identify what is updating the Operational status field. Also, verify the Azure Discovery mapping and review any Business Rules, Flows, or integrations that may be modifying the status. This should help identify the root cause before changing the automated patching logic .

 

*********************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb




0 Helpfuls