
MatlockK at exempla
Nov 24, 2009, 6:48 AM
Post #3 of 6
(784 views)
Permalink
|
Another thing to look at is the tacacs source-interface. If you don't have it in there, tie it to a loopback. If you do have it in there, verify the IP of the interface, and also try removing it. I've seen a few times after an upgrade that either removing it, or adding it 'magically' fixed the problem. Ken Matlock Network Analyst Exempla Healthcare (303) 467-4671 matlockk [at] exempla -----Original Message----- From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Ian Henderson Sent: Tuesday, November 24, 2009 6:43 AM To: Mohammad Khalil Cc: cisco-nsp [at] puck Subject: Re: [c-nsp] Metro Ethernet Switches On Tue, 24 Nov 2009, Mohammad Khalil wrote: > the tacacs could not work well as it was in the previous image even > though i had the same configuration any thoughts ? Try adding the plaintext key again ('tacacs-server key xxx'). I've seen some IOS upgrades need it re-obfuscated to make it work. Just copy/pasting the existing obfuscated key won't work. _______________________________________________ cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
|