What happens to log files on the Cisco Content Security Appliance that are pushed via FTP or SCP?

Available Languages

Download Options

  • PDF     (5.8 KB)
    View with Adobe Reader on a variety of devices
Updated:July 22, 2014
Document ID:118047

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Contents

Question

Question

What happens to log files on the Cisco Content Security appliance that are pushed via FTP or SCP?

When a log file reaches its configured "maximum file size", it is renamed from a file ending with the ".c" extension (c = current) to a file ending with a ".s" extension (s = saved). This process is referred to as "rollover."

When you configure logs to be pushed via FTP or SCP, the saved (.s) file is pushed to your specified destination server at rollover time, and then it is deleted from the appliance.

References

For more information about Rolling Over Log Subscriptions, see the AsyncOS User Guide on the Cisco Content Security products support.

Revision History

Revision Publish Date Comments
1.0
22-Jul-2014
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • John Yu and Ivo Sabev
    Cisco TAC Engineers.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products