I have 2 ACS SE-appliances (1113). I'm experiencing lots of problems with the AAA-servers. After (re-)installation, I have different results: sometimes, there are 2 entries in the AAA-servers-list: an ACS01 (name of the appliance) and a "self". But on my second ACS, there is a "ACS02" and "Deliverance01" (in stead of 'Self').
Sometimes, the deliverance01 or self receives a 169.254.x.x address, sometimes a 127.0.0.1 and sometimes it even has an address from the DHCP pool (although I configured the appliance NOT to use DHCP but static addressing!)...
If you try to change names (with the console or by the web interface (appliance configuration), it becomes a total mess: the names sometimes change ,sometimes they don't, sometimes the old names remain in the proxy distribution table although they don't exist in the aaa-servers table anymore.
If you use Database replication (although i have disabled the Network Config Device tables and Distribution table" to be replicated), it sometimes updates the AAA-server tables, then I get 2 entries named "Self", which leads to replication errors, and I cannot delete or change the wrong ones, ...).
Can somebody help me with the following:
What should be exactly in the AAA-servers table after a clean (re-)installation?
Re: ACS SE: what's wrong with the AAA-servers config?
I ran into the identical problem when I tried configuring my two SE's. I ended up opening a TAC case on it. Basically the engineer informed me that the "deliverance01" is the standard default when the machine comes up.
I gamed it by configuring my dhcp server to have a two IP scope and then ensured it assigned the IP address I wanted each SE to have. I then powered them up one at a time.
After they were up, I went into the config's and changed them to static.
It ain't elegant - but it worked. Hope this helps.
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...