The community will be in read-only from Monday 11:59pm (PT) to Wednesday 7:30am (PT)
The community will be in read-only from Monday 11:59pm (PT) to Wednesday 7:30am (PT)
UCMDB and UD Practitioners Forum (Previously CMS)
cancel
Showing results for 
Search instead for 
Did you mean: 

CI Aging query

SOLVED
Go to solution
Highlighted
SriSurya
Super Collector

CI Aging query

I have enabled CI aging in UCMDB, and I see that when I build a TQL query with some defined Ip ranges, it has CIs which was last time accessed a 6 months back, how do I make sure that CI aging is working properly and it is removing all CIs which is no longer discovered.

 

 

P.S. This thread has been moevd from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. - Hp Forum Moderator

6 REPLIES
Amit Erental
Honored Contributor

Re: CI Aging query

Hi,

which version is it ?

make sure you have the info from the "CI Lifecycle and the Aging Mechanism" chapter, "Model management" help.

you need to check the attribute "enable aging" on the CI Instance itself.

Amit
SriSurya
Super Collector

Re: CI Aging query

I am using version 7.50, and i see that under infrastructure settings, aging is enabled.
Amit Erental
Honored Contributor

Re: CI Aging query

Hi,

Yes, thats for the whole aging flow, for the UCMDB system.

check for a specific CI instance properties, if the property (attribute) realted to aging is set to "true"

its all in the doc

BTW, did you followed the instruction to restart UCMDB after the change ?

Amit

Amit Erental
Honored Contributor
Solution

Re: CI Aging query

Hi,

see "Removing Out of Date CIs Using the Aging Mechanism", page 61 for the Model Managememt PDF of 7.5 version
SriSurya
Super Collector

Re: CI Aging query

Hi Amit,
I went through the doc and made the necessary changes, and i am sure that it will work now, if incase any quires i will get back to you.
Thanks for your quick help.
SriSurya
Super Collector

Re: CI Aging query

Went through the doc and Amit's instructions and made changes accordingly
//Add this to "OnDomLoad" event