topic TACACS RANCID Nexus issue - AAA_AUTHOR_STATUS_METHOD=16(0x10) in Network Access Control https://community.cisco.com/t5/network-access-control/tacacs-rancid-nexus-issue-aaa-author-status-method-16-0x10/m-p/2428979#M88351 <P>I recently enabled command authorization on my Nexus switches and RANCID could no longer run. The error rancid reported was:</P><P></P><P>AAA_AUTHOR_STATUS_METHOD=16(0x10)</P><P></P><P>It was weird because the commands RANCID was running, could be ran just fine manually by calling the rancid clogin script. We have different groups setup in TACACS, one for network engineers, and one specifically for RANCID. If I moved the rancid user over to the neteng group it would run fine, so I noticed a difference was a tac_plus.conf stanza present for neteng but missing for rancid:</P><P></P><P>default service = permit</P><P></P><P>Directly underneath the group definition. After adding that to the rancid user, all was well.</P> Mon, 11 Mar 2019 04:21:00 GMT Mister Cartwright 2019-03-11T04:21:00Z TACACS RANCID Nexus issue - AAA_AUTHOR_STATUS_METHOD=16(0x10) https://community.cisco.com/t5/network-access-control/tacacs-rancid-nexus-issue-aaa-author-status-method-16-0x10/m-p/2428979#M88351 <P>I recently enabled command authorization on my Nexus switches and RANCID could no longer run. The error rancid reported was:</P><P></P><P>AAA_AUTHOR_STATUS_METHOD=16(0x10)</P><P></P><P>It was weird because the commands RANCID was running, could be ran just fine manually by calling the rancid clogin script. We have different groups setup in TACACS, one for network engineers, and one specifically for RANCID. If I moved the rancid user over to the neteng group it would run fine, so I noticed a difference was a tac_plus.conf stanza present for neteng but missing for rancid:</P><P></P><P>default service = permit</P><P></P><P>Directly underneath the group definition. After adding that to the rancid user, all was well.</P> Mon, 11 Mar 2019 04:21:00 GMT https://community.cisco.com/t5/network-access-control/tacacs-rancid-nexus-issue-aaa-author-status-method-16-0x10/m-p/2428979#M88351 Mister Cartwright 2019-03-11T04:21:00Z TACACS RANCID Nexus issue - AAA_AUTHOR_STATUS_METHOD=16(0x10) https://community.cisco.com/t5/network-access-control/tacacs-rancid-nexus-issue-aaa-author-status-method-16-0x10/m-p/2428980#M88352 <HTML><HEAD></HEAD><BODY><P>Please check this forum: It is having the full configuration of AAA in Nexus:</P><P></P><P><A class="jive-link-external-small" href="http://www.hellanetwork.com/2013/06/nx-os-security.html">http://www.hellanetwork.com/2013/06/nx-os-security.html</A></P></BODY></HTML> Thu, 06 Feb 2014 06:09:03 GMT https://community.cisco.com/t5/network-access-control/tacacs-rancid-nexus-issue-aaa-author-status-method-16-0x10/m-p/2428980#M88352 Naveen Kumar 2014-02-06T06:09:03Z