<?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 Hi,I would request you to in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692122#M190769</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would request you to check the status of the TACACS server on the ASA device ?&lt;/P&gt;&lt;P&gt;Also , try to test the username and password against the TACACS and see if it works ?&lt;/P&gt;&lt;P&gt;show aaa-server&lt;/P&gt;&lt;P&gt;test aaa authentication &amp;lt;server name&amp;gt; username password&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jun 2015 16:56:28 GMT</pubDate>
    <dc:creator>Vibhor Amrodia</dc:creator>
    <dc:date>2015-06-11T16:56:28Z</dc:date>
    <item>
      <title>Why cannot tacacs users access failover ASA ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692119#M190763</link>
      <description>&lt;P&gt;Dear All&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: rgb(34, 34, 34); font-family: 'Open Sans', sans-serif; font-size: 14px; line-height: 22px;"&gt;We set up failover ASA. but the tacacs users cannot access failover ASA5555 ? when the user access the ASA, the password do not work. In order to solve the problem, I create new username in the ASA, and then the new user can access the ASA. At same time, tacacs users can access other devices, which means tacacs ACS is working well. Any one can give me some suggestion ? Thank you&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 01:08:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692119#M190763</guid>
      <dc:creator>wfqk</dc:creator>
      <dc:date>2019-03-13T01:08:23Z</dc:date>
    </item>
    <item>
      <title>Hi,Can you share with us the</title>
      <link>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692120#M190766</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can you share with us the ASA AAA configuration please ? From the looks of the issue , it seems that the AAA authentication is only looking at the LOCAL database and not TACACS&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jun 2015 14:38:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692120#M190766</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-06-10T14:38:38Z</dc:date>
    </item>
    <item>
      <title>Hi Vibhor,Thank you so much</title>
      <link>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692121#M190768</link>
      <description>&lt;P&gt;Hi Vibhor,&lt;/P&gt;&lt;P&gt;Thank you so much for your reply. Right,&amp;nbsp;the AAA authentication is only looking at the LOCAL database and not TACACS. The below is failover and SSH configuration, which I simplified since it is for production. Please let me know if you need any info.&lt;/P&gt;&lt;P&gt;--------------------------------------------&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/0&lt;/P&gt;&lt;P&gt;&amp;nbsp;description "Connections to C1 eth8/20"&lt;/P&gt;&lt;P&gt;&amp;nbsp;channel-group 1 mode on&lt;/P&gt;&lt;P&gt;&amp;nbsp;no nameif&lt;/P&gt;&lt;P&gt;&amp;nbsp;no security-level&lt;/P&gt;&lt;P&gt;&amp;nbsp;no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/1&lt;/P&gt;&lt;P&gt;&amp;nbsp;description "Connections to C1 eth8/21"&lt;/P&gt;&lt;P&gt;&amp;nbsp;channel-group 1 mode on&lt;/P&gt;&lt;P&gt;&amp;nbsp;no nameif&lt;/P&gt;&lt;P&gt;&amp;nbsp;no security-level&lt;/P&gt;&lt;P&gt;&amp;nbsp;no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2&lt;/P&gt;&lt;P&gt;&amp;nbsp;description "Connections to C1 eth8/22"&lt;/P&gt;&lt;P&gt;&amp;nbsp;channel-group 1 mode on&lt;/P&gt;&lt;P&gt;&amp;nbsp;no nameif&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;no security-level&lt;/P&gt;&lt;P&gt;&amp;nbsp;no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/3&lt;/P&gt;&lt;P&gt;&amp;nbsp;description "Connections to C1 eth8/23"&lt;/P&gt;&lt;P&gt;&amp;nbsp;channel-group 1 mode on&lt;/P&gt;&lt;P&gt;&amp;nbsp;no nameif&lt;/P&gt;&lt;P&gt;&amp;nbsp;no security-level&lt;/P&gt;&lt;P&gt;&amp;nbsp;no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/7&lt;/P&gt;&lt;P&gt;&amp;nbsp;description LAN Failover Interface&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Management0/0&lt;/P&gt;&lt;P&gt;&amp;nbsp;management-only&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif management&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 10.20.10.65&amp;nbsp;255.255.255.0 standby 10.20.10.66&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Port-channel1&lt;/P&gt;&lt;P&gt;&amp;nbsp;description EtherChannel to C1&lt;/P&gt;&lt;P&gt;&amp;nbsp;no nameif&lt;/P&gt;&lt;P&gt;&amp;nbsp;no security-level&lt;/P&gt;&lt;P&gt;&amp;nbsp;no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Port-channel1.2&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;description Outside to Internet 215.113.16.0/24&lt;/P&gt;&lt;P&gt;&amp;nbsp;shutdown&lt;/P&gt;&lt;P&gt;&amp;nbsp;vlan 20&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif outside&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 215.113.16.250 255.255.255.0 standby 215.113.16.251&amp;nbsp;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Port-channel1.9&lt;/P&gt;&lt;P&gt;shutdown&lt;/P&gt;&lt;P&gt;&amp;nbsp;vlan 99&lt;/P&gt;&lt;P&gt;&amp;nbsp;nameif inside&lt;/P&gt;&lt;P&gt;&amp;nbsp;security-level 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;ip address 10.20.2.250 255.255.255.0 standby 10.20.2.251&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 (management) host 10.20.6.10&lt;/P&gt;&lt;P&gt;user-identity default-domain LOCAL&lt;/P&gt;&lt;P&gt;aaa authentication ssh console tacacs LOCAL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ssh 0.0.0.0 0.0.0.0 management&lt;/P&gt;&lt;P&gt;ssh timeout 5&lt;/P&gt;&lt;P&gt;ssh key-exchange group dh-group1-sha1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;I used the command ---&amp;nbsp;crypto key generate rsa modulus 1024, but show run does not show it&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jun 2015 19:53:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692121#M190768</guid>
      <dc:creator>wfqk</dc:creator>
      <dc:date>2015-06-10T19:53:33Z</dc:date>
    </item>
    <item>
      <title>Hi,I would request you to</title>
      <link>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692122#M190769</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would request you to check the status of the TACACS server on the ASA device ?&lt;/P&gt;&lt;P&gt;Also , try to test the username and password against the TACACS and see if it works ?&lt;/P&gt;&lt;P&gt;show aaa-server&lt;/P&gt;&lt;P&gt;test aaa authentication &amp;lt;server name&amp;gt; username password&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2015 16:56:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cannot-tacacs-users-access-failover-asa/m-p/2692122#M190769</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-06-11T16:56:28Z</dc:date>
    </item>
  </channel>
</rss>

