OOB functionality between install status and Operational status for CMDB VM Instance Table records

[Abby1]

Hi Team,

Just wanted to understand what is the OOB functionality between the Install status and Operational status for cmdb VM Instance table records as we are facing an issue where the installed status of the VM instance records changes to retired but the Operational status changes to non-operational status. What would be the OOB functionality when the install status changes for VMI and what are the OOB rules which triggers the sttaus change  between install status and ops status ?

Any inputs will be appriciated. 

Thanks,

Abby

[Dr Atul G- LNG]

Hi @Abby1 

https://youtu.be/pQGbtRZ6W1w

https://youtu.be/LnIidLxdw8A

These video will give you end to end clarity.

[Tanushree Maiti]

Hi @Abby1 

Check This KB: KB1641149 The business rule "Sync ops status for CMDB CI" is not syncing values across Hardware Stat... 

In the "VM instance state and status fields" document, the Business Rule 'Sync ops status for CMDB CI' lists the following fields;

Operational status
Hardware status
Install status

In practice however all 3 fields may not appear to be in sync. As an example, take a cmdb_ci_server record with all 3 fields set as installed/operational. Manually set the field operational_status = retired, the hardware_status field will sync to also show retired. The install_status field remains unchanged. The reason the server is only syncing operational status and hardware status is due to the logic defined in the Business Rule for hardware vs non-hardware CIs and determining when to sync.


The Sync Ops Status for CMDB CI business rule takes different actions if the CI extends the cmdb_ci_hardware table, than if it does not. 

If it does extend cmdb_ci_hardware, i.e. is a hardware type CI, then hardware status and operational status are synchronized. The install status is not updated by this business rule when this logic is applied. 

If it does not extend cmdb_ci_hardware, a non-hardware CI, instead the install status field is synchronized with operational status. The Hardware Status is not updated by this business rule when this logic is applied. 

Additionally, this doesn't sync all status values. It only applies if operational_status and the appropriate "other" status field (based on the logic above) are mismatched on a retired value. Specifically, we only sync if operational_status is retired and the other field is not, or if the other field is retired and operational_status is not.