<?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 upgrade in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627013#M575264</link>
    <description>&lt;P&gt;We are having sns3595 medium vm with release 2.4 ISE box. We are planning to upgrade to ISE release 2.7 sns3595.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the cisco document, it was mentioned that the compatible RHEL release is 7.6 for ISE version 2.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As per the linux team, we got the confirmation that they are having linux Server with RHEL 7.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If i download the upgrade bundle from cisco for relaese 2.7 , would that be compatible with server requirements.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jun 2022 11:05:38 GMT</pubDate>
    <dc:creator>sujanyakj</dc:creator>
    <dc:date>2022-06-07T11:05:38Z</dc:date>
    <item>
      <title>ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627013#M575264</link>
      <description>&lt;P&gt;We are having sns3595 medium vm with release 2.4 ISE box. We are planning to upgrade to ISE release 2.7 sns3595.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the cisco document, it was mentioned that the compatible RHEL release is 7.6 for ISE version 2.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As per the linux team, we got the confirmation that they are having linux Server with RHEL 7.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If i download the upgrade bundle from cisco for relaese 2.7 , would that be compatible with server requirements.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 11:05:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627013#M575264</guid>
      <dc:creator>sujanyakj</dc:creator>
      <dc:date>2022-06-07T11:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627163#M575270</link>
      <description>&lt;P&gt;Why are you upgrading to ISE 2.7?&amp;nbsp;&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2943876.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2943876.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You should upgrade to 3.1.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It would also be advisable to redeploy the 36XX 3.1 OVA from scratch and then import the ISE configuration backup.&amp;nbsp; Rather than upgrade your existing VM.&lt;/P&gt;
&lt;P&gt;Only ISE 2.6 and later can upgrade to 3.1.&amp;nbsp; So you will need to deploy a new 2.6 node, import 2.4 backup, backup 2.6, and then import 2.6 config into 3.1.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 13:36:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627163#M575270</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-06-07T13:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627235#M575277</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have plans to move to 3.1 release in future as it dependency on VM common license.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 15:06:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627235#M575277</guid>
      <dc:creator>sujanyakj</dc:creator>
      <dc:date>2022-06-07T15:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627407#M575283</link>
      <description>&lt;P&gt;So why spend the effort now to move 2.7 on an old VM license?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 18:24:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627407#M575283</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-06-07T18:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627574#M575294</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1343515"&gt;@sujanyakj&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;1st&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;. &lt;STRONG&gt;ISE 3.1&lt;/STRONG&gt; supports upgrade from: &lt;STRONG&gt;2.6+&lt;/STRONG&gt;.&lt;BR /&gt;. &lt;STRONG&gt;ISE 2.7&lt;/STRONG&gt; supports upgrade from: &lt;STRONG&gt;2.2+&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;2nd&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;. &lt;STRONG&gt;Release 3.1&lt;/STRONG&gt; supports &lt;STRONG&gt;RHEL 8.2&lt;/STRONG&gt;.&lt;BR /&gt;. &lt;STRONG&gt;Release 2.7&lt;/STRONG&gt; supports &lt;STRONG&gt;RHEL 7.6&lt;/STRONG&gt;.&lt;BR /&gt;. &lt;STRONG&gt;Release 2.4&lt;/STRONG&gt; supports &lt;STRONG&gt;RHEL 7.3&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;3rd&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;. &lt;STRONG&gt;ISE 3.0+&lt;/STRONG&gt; ONLY supports &lt;STRONG&gt;Smart Licensing&lt;/STRONG&gt; !!!&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;. If you’re using the &lt;STRONG&gt;Old VM License&lt;/STRONG&gt; (i.e., &lt;STRONG&gt;R-ISE-5VM-K9=&lt;/STRONG&gt;), you should migrate the &lt;STRONG&gt;Old VM License&lt;/STRONG&gt; to the &lt;STRONG&gt;legacy VM Medium License&lt;/STRONG&gt; (&lt;STRONG&gt;R-ISE-VMM-K9=&lt;/STRONG&gt;) and then migrate the &lt;STRONG&gt;legacy VM Medium License&lt;/STRONG&gt; to the &lt;STRONG&gt;VM Common License&lt;/STRONG&gt; !!!&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;. &lt;STRONG&gt;Customers&lt;/STRONG&gt; who are on &lt;STRONG&gt;ISE 2.X&lt;/STRONG&gt; and &lt;STRONG&gt;ISE 3.0&lt;/STRONG&gt; can continue to use the &lt;STRONG&gt;legacy VM Licenses&lt;/STRONG&gt; until the &lt;STRONG&gt;EOL Date&lt;/STRONG&gt; of the &lt;STRONG&gt;Licenses&lt;/STRONG&gt;. They also can migrate the &lt;STRONG&gt;legacy VM Licenses&lt;/STRONG&gt; to the &lt;STRONG&gt;VM Common License&lt;/STRONG&gt; and stay on &lt;STRONG&gt;ISE 2.X&lt;/STRONG&gt; or &lt;STRONG&gt;ISE 3.0&lt;/STRONG&gt; !!!&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 03:31:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/4627574#M575294</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2022-06-08T03:31:30Z</dc:date>
    </item>
  </channel>
</rss>

