09-20-2010 01:27 AM - edited 03-06-2019 01:04 PM
I've got L2 switch with a secondary IP address configured (for management purposes), it's connected to a ADSL router and we're 'natting' on the router to the secondary IP address - all seems to be working OK.
When we apply aaa to the L2 switch, it doesn't seem to respond to the tacacs server - does tacacs always work to the primary ip address ? or is there a way to communicate with the secondary address ?
Solved! Go to Solution.
09-26-2010 09:42 AM
Hello.
Please try using ip tacacs source-interface
Hope this helps.
09-26-2010 09:42 AM
Hello.
Please try using ip tacacs source-interface
Hope this helps.
09-27-2010 12:56 AM
Thanks...just tryied this morning and all working OK now.
03-14-2011 09:44 AM
> lease try using ip tacacs source-interface
How do you do that?
As far as I see you can't assign IP-addresses as source-interface (at least with IOSs we're using):
To use the IP address of a specified interface for all outgoing TACACS+ packets, use the ip tacacs source-interface command in global configuration mode. Use the no form of this command to disable use of the specified interface IP address.
ip tacacs source-interface subinterface-name
no ip tacacs source-interface
subinterface-name | Name of the interface that TACACS+ uses for all of its outgoing packets. |
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: