<?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: Deploying ISE with TACACS, PPP and ISDN in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3775300#M486715</link>
    <description>&lt;P&gt;Adding to &lt;A href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532" target="_blank"&gt;Arne Bier&lt;/A&gt;'s&amp;nbsp;...&lt;/P&gt;
&lt;P&gt;What really needed is to debug on the network device, the one providing the ISDN dial-in, itself and see why it disconnecting the session. You would probably need to contact the vendor or the platform support for that network device.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Jan 2019 17:45:53 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2019-01-08T17:45:53Z</dc:date>
    <item>
      <title>Deploying ISE with TACACS, PPP and ISDN</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3774063#M486551</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;i am currently struggling with the migration of a ACS/TACACS based ISDN dial in solution to ISE 2.3.&lt;/P&gt;
&lt;P&gt;My problem is finding the missing bits under ISE. And if it's generally supported or works at all.&lt;/P&gt;
&lt;P&gt;I have configured a couple of Cisco AV-pairs e.g. protocol=lcp,ip,multilink....debug tacacs shows me that the attributes are accepted by the router, but for some reason the router is disconnecting the ppp session:-(&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there anyone who has a running setup with ISE &amp;amp; TACACS &amp;amp; PPP/CHAP &amp;amp; ISDN?&lt;/P&gt;
&lt;P&gt;I would be very thankful for documentation hints or any experience for such a setup!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Christian&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jan 2019 11:46:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3774063#M486551</guid>
      <dc:creator>cgrodde</dc:creator>
      <dc:date>2019-01-07T11:46:05Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying ISE with TACACS, PPP and ISDN</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3774473#M486710</link>
      <description>&lt;P&gt;I have not used TACACS with PPP ... but if the ACS system is still around, have you considered capturing a tcpdump on the ACS server CLI and then analyzing (comparing) it with the ISE tcpdump that is failing?&amp;nbsp; Sometimes having a side by side comparison may be helpful.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the TACACS return traffic to the NAS is identical, then it could be some lingering ACS config on the NAS that needs to change (or be brought in line for ISE IP address etc.).&amp;nbsp; E.g. using a RADIUS analogy,&amp;nbsp; it's easy to overlook changing the CoA IP address on the NAS ... &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt; and then wonder why the new Radius server doesn't do what the old one did.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jan 2019 22:02:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3774473#M486710</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-01-07T22:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying ISE with TACACS, PPP and ISDN</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3775300#M486715</link>
      <description>&lt;P&gt;Adding to &lt;A href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532" target="_blank"&gt;Arne Bier&lt;/A&gt;'s&amp;nbsp;...&lt;/P&gt;
&lt;P&gt;What really needed is to debug on the network device, the one providing the ISDN dial-in, itself and see why it disconnecting the session. You would probably need to contact the vendor or the platform support for that network device.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 17:45:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-with-tacacs-ppp-and-isdn/m-p/3775300#M486715</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-01-08T17:45:53Z</dc:date>
    </item>
  </channel>
</rss>

