- Bronze, 100 points or more
I use LMS 3.2 with three servers where CS and CM are running on the first server, RME is running on the second one and IPM is running on the third.
The most switches are 3560-24PS-S or 3560-48PS-S with IOS 12.2(46)SE.
Since some weeks I have the problem, that the usertracking data is not up to date.
end hosts are not discovered by CM. all switches are available for CM and data collection works fine.
data collection is running one hour before the user tracking major collection. I scheduled three major runs a day and minor acquisition every 60 minutes.
there are 56000 entries in the UT database, but only 29000 end hosts have a valid "last seen date". the other 27000 hosts have a date of july 2009. the delete intervall is 60 days after every major update. I don't know why they are in the database. some of them have the state "active".
How I can clean the UT database safely so I don't have any old entries in it when I start a new discovery?
One fundamental question: Is it better to use the UT dicovery cycles or to send MAC-notification traps to the CM server?
I think to send traps could be the better way because on a NAC it works fine, too.
Thanks for any advise.