I am running LMS 2.5.1 on Solaris 9 and trying to reclaim database space in the three syslog DB files (SyslogFirst.db, SyslogSecond.db, SyslogThird.db) in RME as they have grown excessively. I reduced the number of days to keep to 7. After running: pdterm RMEDbEngine and pdexec RMEDbEngine, I used a class file received from Cisco to reclaim space with the following syntax:
No, shrinking the size of rmeng.db is a much more complex process, and could be a futile task. You need to figure out why the database has grown so large in the first place. If the database contains actual data as opposed to fragmentation, then reloading it will have no effect. The most common cause of database bloat is excessive retention of Change Audit and config records. You should make sure both Change Audit and config purging are configured, and you may want to go through RME > Admin > Inventory > Inventory Change Filter to make sure you are only generating Change Audit records for interesting changes. Additionally, if you have a lot of IOS switches using vlan.dat, you may want to consider enabling the config change filter under RME > Admin > Change Audit > Config Change Filter.
Once you have everything tuned, then you can open a TAC service request to get the instructions for unloading and reloading the RME database. However, it would be safer for TAC to perform these steps over a Meeting Place session.
Tried to shrink the size of syslog[first|second|third].db (explorer.jpg) files after receiving 3,5 million!! syslog a day (syslog.jpg). Forced Syslog Purge was successfull, and switched off FWSM logging.
Now Severity Level Summary report displays approx. 10000 syslogs per day, which is acceptable. But memory usage (task_man.jpg) is still the same, as with 3,5 million syslogs, and .db files size has not changed either. How could i shrind the .db files, to free up some memory?
The size of database or data space files will not shrink. To recover this disk space, you will need to call the TAC and request DBSpaceReclaimer.class. This will drop the syslog data spaces, and recreate them. This will free up the disk space, but you will lose all syslog messages currently in RME.
Whether or not this will lower the rmeng engine's memory footprint is questionable, since some of this cache memory may be caused by other data in the rmeng database.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.