<?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: ISE tacacs+ in distributed environment in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367414#M549242</link>
    <description>&lt;P&gt;Based on my understanding, you need a different license for TACACS on ISE. In fact, I would suggest you ISE 2.3 for TACACS services because there are some details supported on this version and NOT the previous ones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Important to mention that you can assign 2 entries (serial number)&amp;nbsp;to the same license so in case that primary pan fails the secondary can be promoted and no issues with the licensing part would happen. I mean, the license would have the serial number attached of Primary and Secondary PAN.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Apr 2018 14:58:44 GMT</pubDate>
    <dc:creator>ajc</dc:creator>
    <dc:date>2018-04-17T14:58:44Z</dc:date>
    <item>
      <title>ISE tacacs+ in distributed environment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367256#M549239</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I&amp;nbsp;want to have a distributed deployment of ISE using two physical server with one Device Administration license. I am going to load balance TACACS+ and RADIUS requests between primary and secondary ISE nodes by configuring half of the devices to primary and half to secondary.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can someone confirm whether secondary ISE can also respond to TACACS+ requests with same license?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:53:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367256#M549239</guid>
      <dc:creator>vaibhgupta157</dc:creator>
      <dc:date>2020-02-21T18:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: ISE tacacs+ in distributed environment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367279#M549240</link>
      <description>&lt;P&gt;The concept of Primary and Secondary applies to Administration and Monitoring personas, not to the Policy services persona, which will actually be the one that responds to the RADIUS and TACACS requests.&lt;/P&gt;
&lt;P&gt;The Policy Services personas do not use any kind of primary/secondary style failover. If one goes offline, it is up to the network device to detect the failure and switch to using different ISE node.&lt;/P&gt;
&lt;P&gt;The Device Administration licence is per deployment, so yes, all nodes with Policy Service persona enabled will serve TACACS requests, if configured to do so.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 10:44:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367279#M549240</guid>
      <dc:creator>agrissimanis</dc:creator>
      <dc:date>2018-04-17T10:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE tacacs+ in distributed environment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367414#M549242</link>
      <description>&lt;P&gt;Based on my understanding, you need a different license for TACACS on ISE. In fact, I would suggest you ISE 2.3 for TACACS services because there are some details supported on this version and NOT the previous ones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Important to mention that you can assign 2 entries (serial number)&amp;nbsp;to the same license so in case that primary pan fails the secondary can be promoted and no issues with the licensing part would happen. I mean, the license would have the serial number attached of Primary and Secondary PAN.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 14:58:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367414#M549242</guid>
      <dc:creator>ajc</dc:creator>
      <dc:date>2018-04-17T14:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE tacacs+ in distributed environment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367421#M549245</link>
      <description>&lt;P&gt;One more detail. To enable TACACS on ISE , check the following box.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="TACACS.png" style="width: 565px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/10467iF87F23C586D31AC9/image-size/large?v=v2&amp;amp;px=999" role="button" title="TACACS.png" alt="TACACS.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 15:02:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/3367421#M549245</guid>
      <dc:creator>ajc</dc:creator>
      <dc:date>2018-04-17T15:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE tacacs+ in distributed environment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/4011482#M549248</link>
      <description>&lt;P&gt;I am self-admittedly not an ISE expert so with that, I have a question about AAA authentication.&amp;nbsp; Currently all of our switches and network equipment are pointing to&amp;nbsp;tacacs server ISE-PRIMARY which is our Primary Monitoring Node.&amp;nbsp; From what I understand, the "Monitoring Node" doesn't provide TACACS authentication services.&amp;nbsp; Just wondering how this is working but it indeed does.&amp;nbsp; My goal is to point AAA authentication for my network devices to our local Policy Services Node.&amp;nbsp; Any help would be appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2020 20:21:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/4011482#M549248</guid>
      <dc:creator>ghdowner46</dc:creator>
      <dc:date>2020-01-14T20:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE tacacs+ in distributed environment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/4011958#M549250</link>
      <description>&lt;P&gt;TACACS is just a persona that can be enabled on any ISE node.&amp;nbsp; All roles can run on any node, but that's not necessarily aligned with best practices.&amp;nbsp; It comes down to how the deployment was designed, standalone, hybrid, or distributed.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you only have two nodes then you are running a standalone deployment and it is ok to have device admin running with the mnts.&lt;BR /&gt;&lt;BR /&gt;If you navigate to this page, you can enable/disable personas, you will also see&amp;nbsp;DEVICE ADMIN listed in the services column.&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;DEVICE ADMIN indicates that node has tacacs enabled.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;https://&amp;lt;ise primary ip&amp;gt;/admin/#administration/administration_system/administration_system_deployment&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2020 17:01:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-tacacs-in-distributed-environment/m-p/4011958#M549250</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2020-01-15T17:01:21Z</dc:date>
    </item>
  </channel>
</rss>

