The syslog purge policy removes messages from the RME database. The messages are permanently deleted. The syslog backup policy takes the messages from the database that are going to be purged and archives them to flat files. These syslog files will be written to /var/adm/CSCOpx/files/rme/syslog on Solaris and NMSROOT\files\rme\syslog on Windows. You must make sure casuser can write to these locations, and that there is enough disk space to hold the backup files. By default each file is limited to 100 MB.
The purge policy is configured under RME > Admin > Syslog > Set Purge Policy. The backup polci is configured under RME > Admin > Syslog > Set Backup Policy.
You want the purge files to be large enough to hold all of the messages being aged out of the database. This size will depend on how many messages you get in a day. You can figure an average size of 100 bytes per message.
Once the messages are purged from the database, you will no longer be able to run RME reports against them. You will need to search through the archive files using other tools.
The messages that have not been purged are stored in the syslog data spaces linked to the rmeng database. These files are in NMSROOT/databases/rmeng, but looking at their size is not an accurate indication of the size of the syslogs. There is really no way to tell what that may be exactly.
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.