Dependent CI retirement with CMDB Data Manager

[Amar_Be]

Hi,

In the page related to Dependents CI management ( https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/configuration-manageme...) ,  It is said that dependent CI to retire are added to the table cmdb_dependent_ci_ledger and "Those CIs are set as being ready to retire using the CMDB Data Manager upon approval."

But I can't find any documentation on how those CI are retired by the CMDB Data Manager. It is not possible to create a Retirement rule on that ledger table.

Does anyone have succesfully used this feature?

[bkprasanna]

Hi Ramyashree,

I have already provided the updates in my earlier replies..please check 

Thanks,

Prasanna BK

[bkprasanna]

Let me know if this solution worked for anyone.

[ramyashree1]

Hi all, 

I am trying to utilize the Cascade-retire dependent CIs  out of box feature for below need:

If a server is retired , all dependent ci to be retired. example: Application (A9@sqlau001mel0531) runs on a Windows Server (sqlau001mel0531)  When sqlau001mel0531 is retired, A98_PROD@sqlau00mel0531 would  become orphan dependent CIs. So it has set application (A98_PROD@sqlau00mel0531) to retired.

Business rule After BR: Track “Retired” CIs runs to
check if the CI belongs to a class which has any downstream dependencies.

I have also created custom lifecycle definition with condition like for server class the operational status is non operational. And also updated the BR "Track Retired CI" to trigger when operational status changes to retired.

The CI is added to the CMDB CI End Of Life Ledger [cmdb_ci_end_of_life_ledger] table.

then I can see all dependent ci being listed in ch CI in the CMDB CI End Of Life Ledger [cmdb_ci_end_of_life_ledger] table.

Till this point it works and In data manager I have the conditions and the can seee the matching criteria too.

Also ran the scheduled job CMDB Cascade Retire Dependent CIs 
If there is a dependent relationship with a dependent CI, then that dependent CI is added to the CMDB Dependent CI Ledger [cmdb_dependent_ci_ledger] table
with the Retire action.Also ran the  Scheduled Job CMDB Dependent CI Policy Processor runs  to process the CIs in
the CMDB Dependent CI Ledger [cmdb_dependent_ci_ledger] table.

After the  approval is provided the task will be closed complete. But I see the dependent Ci listed in ledger table still as operational.

Can someone help me to understand this process? Is there a recommended way to approach  this, Any guidance would be greatly appreciated!

Thank you.

[ramyashree1]

Hi all, 

I am trying to utilize the Cascade-retire dependent CIs  out of box feature for below need:

If a server is retired , all dependent ci to be retired. example: Application (A9@sqlau001mel0531) runs on a Windows Server (sqlau001mel0531)  When sqlau001mel0531 is retired, A98_PROD@sqlau00mel0531 would  become orphan dependent CIs. So it has set application (A98_PROD@sqlau00mel0531) to retired.

Business rule After BR: Track “Retired” CIs runs to
check if the CI belongs to a class which has any downstream dependencies.

I have also created custom lifecycle definition with condition like for server class the operational status is non operational. And also updated the BR "Track Retired CI" to trigger when operational status changes to retired.

The CI is added to the CMDB CI End Of Life Ledger [cmdb_ci_end_of_life_ledger] table.

then I can see all dependent ci being listed in ch CI in the CMDB CI End Of Life Ledger [cmdb_ci_end_of_life_ledger] table.

Till this point it works and In data manager I have the conditions and the can seee the matching criteria too.

Also ran the scheduled job CMDB Cascade Retire Dependent CIs 
If there is a dependent relationship with a dependent CI, then that dependent CI is added to the CMDB Dependent CI Ledger [cmdb_dependent_ci_ledger] table
with the Retire action.Also ran the  Scheduled Job CMDB Dependent CI Policy Processor runs  to process the CIs in
the CMDB Dependent CI Ledger [cmdb_dependent_ci_ledger] table.

After the  approval is provided the task will be closed complete. But I see the dependent Ci listed in ledger table still as operational.

Can someone help me to understand this process? Is there a recommended way to approach  this, Any guidance would be greatly appreciated!

Thank you.

[bkprasanna]

Hi Ramyashree,

Once you close the CMDB dependent management task the records will be vanished from ledger table ..try to refresh the ledger table .

Also on your query by using this feature you can set the Life cycle stage cycle and Life cycle status to End of life and Retired..

This feature will not touch the install status or Operational status which will be in its original state.

you can set a BR or Scheduled script to change the Install status to Retired or Operational status to retire for the records whos Life cycle status is changed to Retired by Dependent management feature.

Thanks,

Prasanna BK