<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TACACS+ fallback problem ASA 5520 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/3212221#M343494</link>
    <description>Hi, its because after a tacacs+ server fails it remains inactive.&lt;BR /&gt;&lt;BR /&gt;You got 2 options.&lt;BR /&gt;1. Is to add "reactivation-mode timed" as an commands under "aaa-server TACACS+ protocol tacacs" it will allow your servicer to automaticly re-activated after 30 seconds.&lt;BR /&gt;&lt;BR /&gt;2. Either way you can add  "reactivation-mode depletion" in the same spot; this will only activate the server(s) after all servers in the same pool is failed. &lt;BR /&gt;&lt;BR /&gt;Cheers, Nico</description>
    <pubDate>Tue, 07 Nov 2017 13:05:21 GMT</pubDate>
    <dc:creator>Nicolaj Nielsen</dc:creator>
    <dc:date>2017-11-07T13:05:21Z</dc:date>
    <item>
      <title>TACACS+ fallback problem ASA 5520</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/2312203#M343483</link>
      <description>&lt;P&gt;﻿&lt;/P&gt;&lt;H2&gt;&lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I&amp;nbsp; have configured tacacs in ASA 5520, it is working fine, I can login&amp;nbsp; into ASA with tacacs credentials..authentication is successfull when&amp;nbsp; tacacs server is unreachable Local authentication is also&amp;nbsp; successfull.....&lt;SPAN style="color: #ff0000;"&gt;&lt;STRONG&gt;But after that when Tacacs server is reachable again...I am not able to login with tacacs credentials&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the the bug of Cisco ASA 5520 software image?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below are the configurations:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ protocol tacacs+&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ (inside) host 1.1.1.1&lt;/P&gt;&lt;P&gt;key tacacs_key&lt;/P&gt;&lt;P&gt;aaa authentication enable console TACACS+ LOCAL&lt;/P&gt;&lt;P&gt;aaa authentication http console TACACS+ LOCAL&lt;/P&gt;&lt;P&gt;aaa authentication serial console LOCAL&lt;/P&gt;&lt;P&gt;aaa authentication ssh console TACACS+ LOCAL&lt;/P&gt;&lt;P&gt;aaa accounting enable console TACACS+&lt;/P&gt;&lt;P&gt;aaa accounting ssh console TACACS+&lt;/P&gt;&lt;P&gt;aaa accounting command privilege 15 TACACS+&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:34:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/2312203#M343483</guid>
      <dc:creator>arun.stha</dc:creator>
      <dc:date>2019-03-12T02:34:17Z</dc:date>
    </item>
    <item>
      <title>TACACS+ fallback problem ASA 5520</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/2312204#M343486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you take captures on inside interface of ASA when problem occurs? Put the captures in pcap.&lt;/P&gt;&lt;P&gt;Paste debug level logs from ASA and logs from ACS when issue is seen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sourav Kakkar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 17:51:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/2312204#M343486</guid>
      <dc:creator>sokakkar</dc:creator>
      <dc:date>2013-09-11T17:51:33Z</dc:date>
    </item>
    <item>
      <title>TACACS+ fallback problem ASA 5520</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/2312205#M343490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Arun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you share the following command with us when the AAA authentication against the tacacs+ database is not working&lt;/P&gt;&lt;P&gt;show aaa-server TACACS+&amp;nbsp; host 1.1.1.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For more information about Core and Security Networking follow my website at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;SPAN&gt;Any question contact me at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2013 19:27:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/2312205#M343490</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-09-11T19:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS+ fallback problem ASA 5520</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/3212221#M343494</link>
      <description>Hi, its because after a tacacs+ server fails it remains inactive.&lt;BR /&gt;&lt;BR /&gt;You got 2 options.&lt;BR /&gt;1. Is to add "reactivation-mode timed" as an commands under "aaa-server TACACS+ protocol tacacs" it will allow your servicer to automaticly re-activated after 30 seconds.&lt;BR /&gt;&lt;BR /&gt;2. Either way you can add  "reactivation-mode depletion" in the same spot; this will only activate the server(s) after all servers in the same pool is failed. &lt;BR /&gt;&lt;BR /&gt;Cheers, Nico</description>
      <pubDate>Tue, 07 Nov 2017 13:05:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-fallback-problem-asa-5520/m-p/3212221#M343494</guid>
      <dc:creator>Nicolaj Nielsen</dc:creator>
      <dc:date>2017-11-07T13:05:21Z</dc:date>
    </item>
  </channel>
</rss>

