logging on the log collector stopped working. After restarting the logging process in the cluster, logging on the log collector started working again and I restored the missing logs from backup.
A few days ago the log collector stopped workng again - no logs at all (nothing live or historic. I restarted the log collector ACS VM and it started logging again but logs prior to the restart are missing.
The ACS cluster is logging to syslog but I really need to have reliable logs on the ACS.
I'm aware of a recent patch for 5.5 but the release notes don't seem to mention the above issue.
I noticed that when the issue occurred, the log collector had somehow disabled Incremental Backup. I re-enabled this and ran a full backup. This took longer than expected ( as I could only see todays logs on the log collector). When finished, the backup file size on the FTP server was nearly 9GB - when I checked the log collector I could see all the historic logs had reappeared!
When the backup finished, the primary ACS in the cluster pegged at 100% CPU - I'll open a TAC case for this.
Yes, this option is enabled but isn't this for when the log-collector is briefly unavailable to receive logs from other ACS servers in the cluster? 180 days worth of logs were going missing from the log collector and then reappearing.
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...