Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Acclaimed Contributor.. Harald Acclaimed Contributor..
Acclaimed Contributor..
200 views

CI Aging does not work

We are using OMi 10.63 and a DFP to sync CIs. We have seen that there are a lot of "old" Cis which are not synced any more. The DFP did not delete them but they are also not deleted from RTSM (Ci Aging).

There is a Last Modified and Last Access Time for the CI. The Last Access Time is updated on a 1-2 day basis, the Last Modified Time is about 6 month old (which is ok) 

The target system (DFP) does not include the CI anymore. We also do not have any events for this CI. The CI History does not show anything.

Therefore: Who is updating this CI? Why does it not "age"?

Kind regards,
Harald

0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Re: CI Aging does not work

Hi Harald,

OM topology sync or topology from the agent is automatically touched every 24 hours.  It deletes a CI if an explicit instance deletion request is sent.  For example, in OM you delete a node, then it triggers a delete in OBM.  Or, an agent policy detects that something that was there is no longer there after checking 5 times in a row, so it triggers an instance deletion request for that object.  If you are referring to the topology that the agent generates without any policy, then there is no deletion sent, so it will continue to get touched every 24 hours.

CP.

0 Likes
Acclaimed Contributor.. Harald Acclaimed Contributor..
Acclaimed Contributor..

Re: CI Aging does not work

 

@Carol: thanks for the response. But we do not have OM nor an Agent. I am talking about DFP sync from an external CMDB.

We do not see any CIs in the "delete candidates"  but there should be. There are a lot of "old" CIs which are not synced anymore. But OMi still "touches" them...

 

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CI Aging does not work

CIs are not aging because Last Access TIme is 1-2 days ago so would not be a candidate for deletion.  So the question is what is touching the CIs.  For CIs sync'd via an Integration Point, when the job runs successfully it will touch the CIs which updates the Last Access Time.  Since you said they are not included in the Integration Point sync job, that would not be the reason.  But you could try clearing the DFP cache just to be sure.

CP.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.