<?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 ISE 2.7 upgrade to version 3 patch 4 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811163#M581039</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;We are currently using Cisco ISE 2.7 version patch 8 and planning to upgrade to version 3.1 Please let me know whether any known issues reported in patch 4 ? A&lt;SPAN&gt;&lt;SPAN class=""&gt;re there any reported issues during the upgrade such as configuration sync etc..&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2023 12:36:06 GMT</pubDate>
    <dc:creator>Gouthami Nair</dc:creator>
    <dc:date>2023-04-10T12:36:06Z</dc:date>
    <item>
      <title>ISE 2.7 upgrade to version 3 patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811163#M581039</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;We are currently using Cisco ISE 2.7 version patch 8 and planning to upgrade to version 3.1 Please let me know whether any known issues reported in patch 4 ? A&lt;SPAN&gt;&lt;SPAN class=""&gt;re there any reported issues during the upgrade such as configuration sync etc..&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 12:36:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811163#M581039</guid>
      <dc:creator>Gouthami Nair</dc:creator>
      <dc:date>2023-04-10T12:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 upgrade to version 3 patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811188#M581043</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1490219"&gt;@Gouthami Nair&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;I didn't have issues from &lt;STRONG&gt;2.7 P8&lt;/STRONG&gt; (&lt;EM&gt;Nov 21th&lt;/EM&gt;) to &lt;STRONG&gt;3.1 P4&lt;/STRONG&gt; (&lt;EM&gt;Sep 22nd&lt;/EM&gt;).&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Note: attention to the following&lt;/P&gt;
&lt;UL class="lia-list-style-type-disc"&gt;
&lt;LI&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd45843" target="_blank" rel="noopener"&gt;CSCwd45843 Auth Step latency for policy evaluation due to Garbage Collection activity&lt;/A&gt;., solved in &lt;STRONG&gt;3.1 P5&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc74531" target="_blank" rel="noopener"&gt;CSCwc74531 ise hourly cron should cleanup the cached buffers instead of the 95% memory usage&lt;/A&gt;, solved in &lt;STRONG&gt;3.1 P5&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 13:30:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811188#M581043</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2023-04-10T13:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 upgrade to version 3 patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811490#M581051</link>
      <description>&lt;P&gt;My own personal experience with 3.1p5 was that Cisco Phones whose EAP-TLS certificate was signed by Call Manager (CAPF cert) would fail - ISE was complaining about failed SSL decoding. We had to revert back to patch4 and then the phones started working again.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have not tried patch 6&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 23:25:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811490#M581051</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2023-04-10T23:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 upgrade to version 3 patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811500#M581053</link>
      <description>&lt;P&gt;I would recommend two things for you.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Install 2.7 patch 9 prior to upgrading, this will limit the amount of change you experience going to 3.1 since many of the fixes in 2.7p9 are also built in to the 3.1 patches.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Target 3.1 patch 6 as your post upgrade release. Patch 6 includes an additional 87 publicly acknowledged bug fixes and a few that are quite severe in p5 hit. It also provides for the workaround with TPM stored certs on windows machines.&amp;nbsp;&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 10 Apr 2023 23:39:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-upgrade-to-version-3-patch-4/m-p/4811500#M581053</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2023-04-10T23:39:16Z</dc:date>
    </item>
  </channel>
</rss>

