OOB operational status for Virtual machine instance class

[B_30]

Can someone point me to the documentation that states how Operational Status is driven on the Virtual Machine instance class (OOTB)?  

We have VMs with State = Terminated and the Operational Status is showing as Operational for most and Non-operational for a handful.

We also VMs with State = Off and the Operational Status is showing between Operational and Non-operational. I haven't been able to identify a pattern.. we haven't done any changes to OOB CI Lifecycle management to date so why are these different by default in so many cases..? 

I don't see an obvious pattern.. Appreciate the help in advance. 

[GB14]

Hello,

You can review this document & also there are a few BR in SN 
https://YOUR INSTANCE.service-now.com/sys_script_list.do?sysparm_query=collection%3Dcmdb_ci_vm_instance&sysparm_view=

Thanks,
G

[Vincent Messier]

Did something changed recently about this ? The doc now says :

VM deleted from vCenter

If the VM is deleted from vCener, the cmdb_ci_vm_instance state changes to terminated and the Status field changes to retired.

The Install status is changing to retired when the state is terminated but the operational status is not updating. Which also result in BR Cascade deprovisioned status to Server to not trigger.

[Rahul Priyadars]

Are u using Mid Server Vcenter event collector for the Synching?

Regards

RP

[Vincent Messier]

Yes we use Mid Server Vcenter event collector. State and Install status is synching when instance are deleted in vCenter but not the operational status.

Comparing GB14 screenshot with the actual doc it looks like it's changed from Operational status to install status as the field beein updated. Just want to confirm it's the case.