You have not provided much for us to work with. Based on your description I would think that the problem might be one of these things:
- perhaps the switch configuration for the tacacs server is not correct?
- perhaps the switch configuration of the shared key with the tacacs server is not correct?
- perhaps the IP address chosen by the switch as the source for the tacacs request is not the same address that is configured on the tacacs server for this client.
- perhaps there is some error in the switch configuration for tacacs configuration.
I would suggest that a good place to start investigating this issue is in the logs of the tacacs server. Is the server seeing the authentication request? If so then there may be some error code that indicates what the problem is. If the server is not seeing the request then it point to a different kind of problem.
It would also be helpful to post the switch config so we can check for issues in the switch config.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...