Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have e Cisco Prime LMS 4.2, whose IpmDbEngine is consuming around 8k RAM.The IPM database is around 9 GB in size, and when trying to query reports, I can get reports from more than a year.This means that IPM purge is not working. Can anybody help? ...
Hi,I have installed RSAC 4.3.0, on a remote Win 2008 server, and it working fine. All devices are sending logs to this server, and "Collector Status", on the local LMS 3.2, is receiving logs fine from this RSAC server. Now the problem is:How can I pu...
Hi all,I am facing a problem with TFTP server of LMS 3.2. While I'm performing sync-archive (under RME), .cofig files are being generated under TFTPboot directory, for almost every device, but they are all empty files (0 KB in size). While trying to ...
Hi support team,I have installed LMS 3.2 on a Win Server 2008, with 160 GB HDD. But it seems that it is running out of space after some times.So actually we managed to add another server, with a HDD of 500 GB capacity, and maped this HDD as a network...
Hi Afroz, Thank you for your reply, but maybe I was not clear. You already explained the detailed steps to re-initialize the IPM database. But what I wanted to know is there any possibility to re-initialize/restart the "data purge" process. It is alw...
Hi Afrahmad,Thank you for your feedback. I will use database re-initialize as a last resort.I tried to purge the database using "Admin > Network > Purge Settings >IPSLA data Purge Settings", but no results. It seems that purge process is not working...
Hi Vinod,With logrot utility, the problem is that the "Maximum Logrot Size = 4096 KB", wich means that if syslog.log goes 4 GB in size, it is deleted, and so will have syslogs saved maybe for 2 days, judging from the rate of increasment of the size o...
Hi Marvin,A tried purging through local LMS 3.2, using RME>Admin>Syslog>Force Purge, but there was no effect at all on the remote syslog.log file. Its strange, somehow if RSAC is a good solution, it should even have some kind of tool to purge this lo...
