<?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 ASA 'failover exec' issue with TACACS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-exec-issue-with-tacacs/m-p/3418677#M134822</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a setup with 2 ASA in failover (active/standby). We want to use the failover exec command. We have a Cisco ISE acting as a TACACS server. Within ISE we control from witch IP the connection come from. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When doin the failover exec command, the standby unit show that the command was initiated form the IP 0.0.0.0 . We do not feel good to put that IP in our ruleset. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is their a workaround.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Jun 2017 14:00:02 GMT</pubDate>
    <dc:creator>PATRICK ROCH</dc:creator>
    <dc:date>2017-06-09T14:00:02Z</dc:date>
    <item>
      <title>ASA 'failover exec' issue with TACACS</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-exec-issue-with-tacacs/m-p/3418677#M134822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a setup with 2 ASA in failover (active/standby). We want to use the failover exec command. We have a Cisco ISE acting as a TACACS server. Within ISE we control from witch IP the connection come from. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When doin the failover exec command, the standby unit show that the command was initiated form the IP 0.0.0.0 . We do not feel good to put that IP in our ruleset. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is their a workaround.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Jun 2017 14:00:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-exec-issue-with-tacacs/m-p/3418677#M134822</guid>
      <dc:creator>PATRICK ROCH</dc:creator>
      <dc:date>2017-06-09T14:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 'failover exec' issue with TACACS</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-exec-issue-with-tacacs/m-p/3418678#M134823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The workaround is: - create a user account "enable_1" on TACACS+ server with any random password; - grant "privilege = 15" and full access on all commands to this user.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jun 2017 12:23:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-exec-issue-with-tacacs/m-p/3418678#M134823</guid>
      <dc:creator>Farhan Mohamed</dc:creator>
      <dc:date>2017-06-12T12:23:21Z</dc:date>
    </item>
  </channel>
</rss>

