02-25-2008 02:08 PM - edited 03-10-2019 03:40 PM
Hi,
i have a 3550 with ipservices 12.2(44) upgraded from c3550-i5q3l2-mz.121-22.EA4.bin when the reload is completed, the switch is no longer authenticating to tacacs and failing back to the local user and password
Solved! Go to Solution.
02-28-2008 11:51 PM
Mini,
Did you define source interface for tacacs authentication.
On router issue command,
ip tacacs source-interface fastethernet x/y , where interface would be the one mentioned in tacacs server.
That should fix it.
Regards,
~JG
Do rate helpful posts
02-26-2008 11:21 AM
Matthew
A logical starting place is to check to see if something in the config changed during the upgrade process. Can you tell us whether anything is different in the config after the upgrade?
Another thing to check is whether the authentication requests are getting to the server. Can you check on the server and see if the server has recognized the authentication attempt (might be in successful log or in failed log).
If those do not provide insight I would suggest running debug tacacs authentication, try to authenticate, and post the debug output.
HTH
Rick
02-28-2008 11:51 PM
Mini,
Did you define source interface for tacacs authentication.
On router issue command,
ip tacacs source-interface fastethernet x/y , where interface would be the one mentioned in tacacs server.
That should fix it.
Regards,
~JG
Do rate helpful posts
03-26-2008 07:09 AM
If you are using aaa group command, you might find its missing from the running config, see CSCsl42964.
03-26-2008 04:57 PM
issue has been fixed,
issue was that post upgrade the device was sending the tacacs+ request out a different interface, so that it was "seeing" the server, but unable to authenticate to it, due to the tacacs+ server having a different IP Address in its database
Thanks to all for the input
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide