BSM RTSM - CI "Last Access Time"

Hi

Running BSM 9.25 and trying to troubleshoot issue with some nodes initially synced from NNMi(10.01) that are completely gone/erased but still has got their Last Access Time property being updated.. We also sync CI's to UCMDB(10.20) which sync back a global ID.

 

Has anyone got experience with similar issues? What is the best way to go about troubleshooting them?

 

br ludvig

Parents
  • If Last Access Time was updated means that they were not deleted by Aging... what shows as "Modified by"?

  • Latest row in modified by in history tab (csv format):

    Apr 1, 2015 4:42:29 PM,DiscoveredLocation,,,"User:nnm-1,LoggedInUser:nnm-1"

     

    Is there any field which keeps track of what is updating the "Last Access Time"? What does the Updated By field contain exactly? I was searching ucmdb documentation to find the meaning of each property but didnt really find anything of value

     

    As said the ID in the field "Node NNM UID" does not exist in NNMi and the physical node is erased completely from any discovery.

     

    This is not a general issue as it is only happening sometimes to a small number of CI's (we have about 800k CI's in rtsm)

  • "Last Updated by" is nnm-1 which is the nnm integration user. As said this ci does not exist in nnmi so it would be very unexpected if it still syncs these devices.. Note that "Last Updated by" is not the same for all ci's experiencing this issue, for some ci's it is some old enrichment we ran at one point in time.

    This is why I did not think "Last Updated by" was directly related to the Last Access Time field updates.

     

     

  • Indeed, if topology was only "refreshed" then LastAccessTime is updated but not "LastUpdatedBy". So, if these CIs are no longer in NNMi maybe they were deleted by the integration?

  • Indeed, if topology was only "refreshed" then LastAccessTime is updated but not "LastUpdatedBy". So, if these CIs are no longer in NNMi maybe they were deleted by the integration?

  • Indeed, if topology was only "refreshed" then LastAccessTime is updated but not "LastUpdatedBy". So, if these CIs are no longer in NNMi maybe they were deleted by the integration?

  • To re-iterate our problem:

    We have CI's in RTSM which should not be in RTSM because they have not existed for the last year or so.

    They exist in no discovery integration.

    Last access time should NOT be refreshed but it is.

    We are trying to troubleshoot why last access time is being refreshed since this keeps them away from aging.

     

     

  • To re-iterate our problem:

    We have CI's in RTSM which should not be in RTSM because they have not existed for the last year or so.

    They exist in no discovery integration.

    Last access time should NOT be refreshed but it is.

    We are trying to troubleshoot why last access time is being refreshed since this keeps them away from aging.

     

     

  • To re-iterate our problem:

    We have CI's in RTSM which should not be in RTSM because they have not existed for the last year or so.

    They exist in no discovery integration.

    Last access time should NOT be refreshed but it is.

    We are trying to troubleshoot why last access time is being refreshed since this keeps them away from aging.

     

     

  • It was not very straightforward to troubleshoot but I believe I have found what is updating the last access time. For some ci's we have set up pattern models which connect ci's with a given pattern to an infrastructure service. For some reason whenever this enrichment is run it updates the last access time of the CI's matching the pattern. So by turning off the enrichment in the scheduler the CI's are no longer being kept from aging.

     

    Is it possible to disable this behavior for pattern model enrichments? Since they are not created as regular enrichments(in enrichment studio) I'm having a hard time finding this feature.

  • It was not very straightforward to troubleshoot but I believe I have found what is updating the last access time. For some ci's we have set up pattern models which connect ci's with a given pattern to an infrastructure service. For some reason whenever this enrichment is run it updates the last access time of the CI's matching the pattern. So by turning off the enrichment in the scheduler the CI's are no longer being kept from aging.

     

    Is it possible to disable this behavior for pattern model enrichments? Since they are not created as regular enrichments(in enrichment studio) I'm having a hard time finding this feature.

  • It was not very straightforward to troubleshoot but I believe I have found what is updating the last access time. For some ci's we have set up pattern models which connect ci's with a given pattern to an infrastructure service. For some reason whenever this enrichment is run it updates the last access time of the CI's matching the pattern. So by turning off the enrichment in the scheduler the CI's are no longer being kept from aging.

     

    Is it possible to disable this behavior for pattern model enrichments? Since they are not created as regular enrichments(in enrichment studio) I'm having a hard time finding this feature.

Reply
  • It was not very straightforward to troubleshoot but I believe I have found what is updating the last access time. For some ci's we have set up pattern models which connect ci's with a given pattern to an infrastructure service. For some reason whenever this enrichment is run it updates the last access time of the CI's matching the pattern. So by turning off the enrichment in the scheduler the CI's are no longer being kept from aging.

     

    Is it possible to disable this behavior for pattern model enrichments? Since they are not created as regular enrichments(in enrichment studio) I'm having a hard time finding this feature.

Children
No Data