<?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 Starting with ISE 2.0, TACACS in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816873#M56417</link>
    <description>&lt;P&gt;Starting with ISE 2.0, TACACS support is introduced. If you have a need for TACACS support, then I would recommend upgrading to 2.0. Also if it's difficult to get maintenance/change windows to upgrade, then I would upgrade to 2.0.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2016 00:06:56 GMT</pubDate>
    <dc:creator>tomyip</dc:creator>
    <dc:date>2016-03-08T00:06:56Z</dc:date>
    <item>
      <title>Upgrade Path from ISE 1.3 : Go to 1.4 or Straight to 2.0?</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816871#M56415</link>
      <description>&lt;P&gt;I am currently running ISE 1.3 in a distribute deployment (2 x PAN/MNT Virtual appliances + 2 x PSN 3495 appliances).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was intent on upgrading to release 1.4.....&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;However, I was looking at all of the cool new fatures in 2.0 (some of which seem beneficial). I also noticed that the first round of patches is out for 2.0, which makes me feel a little better about it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Are there any show stoppers that I should be nervous about?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Phill&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:18:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816871#M56415</guid>
      <dc:creator>phillip.vansickle</dc:creator>
      <dc:date>2019-03-11T06:18:21Z</dc:date>
    </item>
    <item>
      <title>If I had a production 1.3 and</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816872#M56416</link>
      <description>&lt;P&gt;If I had a production 1.3 and was upgrading today, I'd go with the latest 1.4 patch unless there was something compelling for my particualr environment in 2.0.&lt;/P&gt;
&lt;P&gt;The 2.0 patch that's out is very limited in what it fixes. Reference:&amp;nbsp;http://www.cisco.com/c/en/us/td/docs/security/ise/2-0/release_notes/ise20_rn.html#pgfId-611708&lt;/P&gt;
&lt;P&gt;I've seen a few 2.0 bugs that might worry me in a non-greenfield production environment. (i.e not pushing a redirect dACL proeprly)&lt;/P&gt;
&lt;P&gt;Once 2.1 or the next patch releease comes out, I might reconsider.&lt;/P&gt;
&lt;P&gt;A greenfield 2.0 deployment would be more of a thumbs up, subject to pilot deploymnet to test the needed features.&lt;/P&gt;
&lt;P&gt;Just my opinion....&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 03:44:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816872#M56416</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-12-08T03:44:51Z</dc:date>
    </item>
    <item>
      <title>Starting with ISE 2.0, TACACS</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816873#M56417</link>
      <description>&lt;P&gt;Starting with ISE 2.0, TACACS support is introduced. If you have a need for TACACS support, then I would recommend upgrading to 2.0. Also if it's difficult to get maintenance/change windows to upgrade, then I would upgrade to 2.0.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 00:06:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816873#M56417</guid>
      <dc:creator>tomyip</dc:creator>
      <dc:date>2016-03-08T00:06:56Z</dc:date>
    </item>
    <item>
      <title>2.0 Patch 2 resolved the</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816874#M56418</link>
      <description>&lt;P&gt;2.0 Patch 2 resolved the issue I had mentioned previously.&lt;/P&gt;
&lt;P&gt;We've done a couple of 2.0 deployments now without any major issues so far. I spoke with the Cisco internal folks and they concur it's ready for production deployments.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 02:58:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816874#M56418</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2016-03-08T02:58:45Z</dc:date>
    </item>
    <item>
      <title>Thanks for your response. 2.0</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816875#M56419</link>
      <description>&lt;P&gt;Thanks for your response. 2.0 sounds like it is definitely worth looking into.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Phill&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 15:34:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-path-from-ise-1-3-go-to-1-4-or-straight-to-2-0/m-p/2816875#M56419</guid>
      <dc:creator>phillip.vansickle</dc:creator>
      <dc:date>2016-03-08T15:34:59Z</dc:date>
    </item>
  </channel>
</rss>

