You can change the shared secret on the tacacs server and wait for the command authorization to error out and then authorize the command locally. If that doesnt work then you best bet is to reboot the switch.
Make sure that your TACACS+ configuration is correct. If you have shell authorization set configured, make sure they authorize you on this device to provide the commands in configuration terminal. I think it is only a TACACS+ mis-configuration. If the same config worked perfectly on another device, you may be providing different command authorization sets to different devices.
Check your TACACS+ configuration please.
Rating useful replies is more useful than saying "Thank you"
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...