<?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 single-connection in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765053#M486973</link>
    <description>&lt;P&gt;We only have this behaviour on our C3560 devices, so my question remains: on which side do you need to activate the single-connection feature?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lieven&lt;/P&gt;</description>
    <pubDate>Mon, 17 Dec 2018 14:02:23 GMT</pubDate>
    <dc:creator>lni1</dc:creator>
    <dc:date>2018-12-17T14:02:23Z</dc:date>
    <item>
      <title>Tacacs single-connection</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765019#M486971</link>
      <description>&lt;P&gt;Dear Cisco,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After running into the session limit (20k) of our ISE 3495, we followed tacacs recommendation of Cisco TAC to implement single-connection feature:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We encountered some issues during our POC:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;We change the config to : tacacs-server host IP&amp;nbsp;&lt;STRONG&gt;single-connection&lt;/STRONG&gt; key xxx&lt;/LI&gt;
&lt;LI&gt;We try to connect to the switch : NOK (enable &amp;amp; conf mode not possible)&lt;/LI&gt;
&lt;LI&gt;When we check the “single-connection” box in ISE of the device everything works fine again.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This seems to happen on all C3560 (12.2(53)SE2)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there Cisco recommendation concerning where to implement this feature?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;On the switch&lt;/LI&gt;
&lt;LI&gt;On ISE&lt;/LI&gt;
&lt;LI&gt;Both&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Kind regards,&lt;/P&gt;
&lt;P&gt;Lieven Stubbe&lt;/P&gt;
&lt;P&gt;Infrabel&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 13:11:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765019#M486971</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2018-12-17T13:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs single-connection</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765047#M486972</link>
      <description>&lt;P&gt;I think this is expected. You configure the switch single-connection to one side but if you not configure the ISE single connection tick box it will ignore single connection from switch . Thats why it work after you check the tick box.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 13:53:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765047#M486972</guid>
      <dc:creator>ognyan.totev</dc:creator>
      <dc:date>2018-12-17T13:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs single-connection</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765053#M486973</link>
      <description>&lt;P&gt;We only have this behaviour on our C3560 devices, so my question remains: on which side do you need to activate the single-connection feature?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lieven&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 14:02:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765053#M486973</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2018-12-17T14:02:23Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs single-connection</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765054#M486975</link>
      <description>&lt;P&gt;I think on both is correct answer&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 14:03:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3765054#M486975</guid>
      <dc:creator>ognyan.totev</dc:creator>
      <dc:date>2018-12-17T14:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs single-connection</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3767263#M486977</link>
      <description>&lt;P&gt;Hello Cisco,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did some Wireshark and it seems that "both" is the correct answer, when you disable the feature on ISE and/or Switch the TACACS stream is split in several TCP sessions. When active on both ends, everything is in one TCP session.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;/P&gt;
&lt;P&gt;Lieven Stubbe&lt;/P&gt;
&lt;P&gt;Infrabel&lt;/P&gt;</description>
      <pubDate>Thu, 20 Dec 2018 11:41:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3767263#M486977</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2018-12-20T11:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs single-connection</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3908799#M486978</link>
      <description>&lt;P&gt;Any issue with the TACACs server running out of resources with single connect if you have thousands of TACACS clients? &amp;nbsp;I'm thinking 10K to 20k clients, each with a an open TCP connections when single-connection configured.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2019 17:19:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-single-connection/m-p/3908799#M486978</guid>
      <dc:creator>kevink707</dc:creator>
      <dc:date>2019-08-15T17:19:08Z</dc:date>
    </item>
  </channel>
</rss>

