I'd like to know if anyone could identify the cause for the following?
We run two Secure ACS servers v126.96.36.199 (patch 2) one as primary and the other as secondary. This issue also occured in v188.8.131.52. They have no issue with replication between them.
I log onto the primary, and import an AccountActions file for adding new user accounts, which is imported successfully as noted in the RDBMS log and stating the AAA is the primary. Though the user account does not appear in the primary but appears in the secondary.
Under System Configuration -> RDBMS Synchronization Setup, the Synchronization Partners are listed as AAA Servers is primary and Synchronize is secondary.
Can anyone explain why the primary is not being updated or the new user appearing in the list? I can manually create an account on the primary and have it sync successfully to the secondary.
I've attached the accountactions file, which is reduced to one account for testing purposes.
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...