Install and Operational Status

[ollop]

Hi Folks

I kindly ask your experience on these two fields in CMDB, with a very similar label (Install Status and Operational Status), arounded by a single mystery on the purpose. In fact the HI Support simply said;

"As per the OOB, In a base system, the CI's Operational Status field and the Status/Hardware Status (if its hardware) fields are kept synchronized if one of the two fields' values is Retired. When Operational Status of a CI is set to Retired, then the Status/Hardware Status field is automatically set to Retired. In the opposite direction, when the Status/Hardware Status field of a CI is set to Retired, Operational Status is then automatically set to Retired too.

So in general the Install Status is the status about the installation of the CI. For example:   Installed, Pending Installed, Retired, etc. 
Operational Status is more about the operation: Operational, Repair in Progress, DR"

Said that, it's true also that our CMDB is full of CIs with Install Status = Installed, Operational Status = Retired,

Do you have any suggestion to explain? Ideas? Articles?

Thank you in advance for any reply: I promise that if it is useful, I give my thumb up

Cordially

Davide Gandolfi

[Mark Manders]

They are partially correct. BR "Sync Ops Status for CMDB CI" on cmdb_ci does sync some fields, but with a lot of conditions. On a server I can change the operational status to 'retired' and the install status will do the same. The other way around is not synced. So that explains your CIs with different field values. 

They are also correct about the operational status being more for using on operational level and the installation status on whether it's installed or not. It can be installed and in repair as example. 

Check on the BR I mentioned to see what it does and when and maybe update it to your own logic.

[ollop]

Hi Mark,

I appreciated in special way your quick answer. Many thanks.

To be honest, the support mentioned a BR but it was "Cascade deprovisioned status to server"; your suggestion  promises better results....

Therefore, if I'm understanding yout thoughts deeply the answer is: if something - and we don't know the use case - changes the Install Status in "Installed" when the Operational Status is "Retired", there isn't any logic to manage it. This explains my CIs and it's shorter for sure to put our logic inside the "Sync Ops Status for CMDB CI" in comparison to get the out of the box algorithm

Am I right? It makes sense..... 

Let me know if I got the point and for me it's clear

Regards

Davide Gandolfi 

[ollop]

Hi @Mark Manders 

I don't know if you had the time to read my interpretation of your post.

Please, let me know if I'm right or not about your thoughts 

Cheers

Davide Gandolfi