When we upgraded from ACS 3.1 to 3.2, replication broke. There's a registry fix & patch for that. Basically replication took too long so the CSMon service thought ACS died and would reset the services thus breaking the replication in process. The registry fix allows you to set an interval for the CsMon checking to be long enough to allow replication to complete. Contact TAC, they can fill you in.
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...