05-22-2018 06:24 AM - edited 03-08-2019 03:06 PM
Few devices do not let us run any command after we log in we get an error stating
"% Authorization failed."
Note -
ACS configuration applied on routers as per below -
aaa new-model
!
!
aaa group server tacacs+ tacacsgrp
server name ACS2
server name ACS1
!
aaa authentication login default group tacacsgrp local
aaa authentication enable default group tacacsgrp enable
aaa authorization exec default group tacacsgrp local
aaa authorization commands 0 default group tacacsgrp local
aaa authorization commands 1 default group tacacsgrp local
aaa authorization commands 15 default group tacacsgrp local
aaa accounting exec default
action-type start-stop
group tacacs+
group tacacsgrp
!
aaa accounting commands 0 default
action-type start-stop
group tacacs+
group tacacsgrp
!
aaa accounting commands 1 default
action-type start-stop
group tacacs+
group tacacsgrp
!
aaa accounting commands 15 default
action-type start-stop
group tacacs+
group tacacsgrp
!
aaa accounting network default
action-type start-stop
group tacacs+
group tacacsgrp
!
aaa accounting system default start-stop group tacacsgrp
!
!
!
!
!
aaa session-id common
tacacs server ACS1
address ipv4 10.X.X.X
key 7 08094D571A340419130
tacacs server ACS2
address ipv4 10.Y.Y.Y
key 7 08094D571A340419130
Can anyone suggest what we have done wrong?
05-22-2018 06:27 AM
05-22-2018 06:29 AM
05-22-2018 06:44 AM
05-22-2018 06:54 AM
05-22-2018 07:02 AM
05-22-2018 08:40 AM
When you login to one of these routers which are having the issue can you tell whether it is authenticating with tacacs credentials or with local credentials? The symptoms suggest that these routers are not communicating with your tacacs server and are doing local authentication and local authorization. If that is the case is it possible that there are issues with the users local credentials?
Your configuration of authorization specifies tacacs as the primary method and local as the secondary method. I have found it helpful to specify if-authenticated as the last method.
HTH
Rick
05-22-2018 11:05 PM
It is indeed authenticating via tacacs credential only and does not accept local credentials.
Only way I can make them work is by removing their IP from ACS server, hence, enforcing access by local accounts then I need to remove dual ACS configuration and point only to primary ACS and it will start authenticating but I do not want to do this.
05-22-2018 11:18 PM
05-22-2018 11:24 PM
All shell profiles have a privilege level of 15. The command set is ruling who gets read-only access and who get read-write.
Also to emphasize other devices sitting in same rules and same shell profile works perfectly.
11-14-2019 01:13 PM - edited 11-14-2019 01:17 PM
11-14-2019 02:03 PM
Hello
@mehulnangru wrote:
Tacacs worked perfectly on all devices when we had a single ACS server and since secondary was added we have seen this issue appearing on few devices.
To validate a possible ACS issue, can you suspend the seconday server and test
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