The application log is the name given in "show ver" for the /usr/ids/idsRoot/var/iplogs partition which for the IPS-4255 is stored in RAM.
On an IPS 4255 the system will automatically create a RAM disk for the partition on bootup, and then the sensor processes will automatically create 512 IPLOG files in the directory.
These 512 files are originally written with empty data, but take up a full 1000000 bytes each.
So these 512 files will automatically fill up the parition 96% full on an IPS-4255.
There are no CLI commands to change this, and none are needed to clean it up. It will always be 96% full.
As new IP Logs are created (in response to the packet log event actions) it will start writing packet data into these 512 IP Log files. When all 512 are full of packet data the sensor will automatically start overwriting the oldest file. So there will always be 512 files and always take up 96% of the partition.
On other sensor models the % used will differ because either the partition size is smaller or larger, and there are smaller or larger number of IP Log files that the sensor creates and uses.
There is no supported method for clearing the IP Logs.
The box can be rebooted in which case all stored information in the IP Logs are lost (remember they were in a RAM disk), and 512 new emtpy files will be created.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...