Your aaa authentication config looks right to me. As I'm sure you know, according to your config, if the ACS is available, then your switch should never look locally for authentication. (If ACS can't find a valid account, it will send back a deny message, and the switch will not allow access, regardless if the user account is present locally) So I'm kinda stuck there.
Any chance you could 'debug aaa authentication,' login and enable, then paste a (sanitized) log results? Otherwise, there should be log entries that say something like:
May 23 15:45:11.888 ZULU: TAC+: (-000000000): received author response status = PASS_ADD
May 23 15:45:11.999 ZULU: AAA/AUTHEN/LOGIN (00000000): Pick method list 'default'
The first one indicates successful communication with the ACS, and the second verifies that TELNET logins map to the default method (aaa authentication login default group tacacs+ local)
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...