I'm trying to add TACACS configuration to two of our WLC's at one of our sites. Our ACS server is running v18.104.22.168.0a and my WLC 5508 is running code version 22.214.171.124.
I have added the TACACS server details to the WLC config (authentication, accounting, and authorisation), which is configured correctly. My ACS box has already been configured to allow the WLC's to authenticate (policy settings etc). We have 4 other identical WLC's on other sites which are already configured to use the same ACS server, which all work.
The problem I am seeing is that the ACS login is being accepted by the ACS box - I can see from the reports that it is accepting the login, but I keep getting re-prompted for a login when attempting to log in to the WLC I just configured. The same happens both on web and SSH console sessions. I am now unable to log in to the WLC with either local or AD credentials (which work on other WLC's on this same ACS box). I've had to hard reboot it to reload the old startup config and gain access again.
The priority order is set to TACACS+ then LOCAL, which is exactly how it's set on the other WLC's.
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...