<?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: ISE licensing question in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627973#M575321</link>
    <description>&lt;P&gt;Assuming your traditional licenses are PAK, and the 2.4 deployment is not using smart licensing, then those licenses will be unaffected. The 2.4 deployment will be unaware of any licensing changes you're making in the smart account or in preparation for 3.x.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#2, reloading the MNT, this will be fine, the 2.4 deployment will run as it always has for you.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jun 2022 15:18:10 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2022-06-08T15:18:10Z</dc:date>
    <item>
      <title>ISE licensing question</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627958#M575320</link>
      <description>&lt;P&gt;we have 2.4 in production with traditional licenses.&lt;/P&gt;
&lt;P&gt;We are building 3.1 in parallel, at some point within few days we will migrate the VMM license to common and base to essential.&lt;/P&gt;
&lt;P&gt;My question to community expert.&lt;/P&gt;
&lt;P&gt;1. There is going to be a month of transition period as we migrate network from 2.4 to 3.1, will the traditional licenses on 2.4 be effected, if we change to common VM and essential, its only for this transition period where we will be running 2.4 with traditional and 3.1 with smart licenses both at the same time.&lt;/P&gt;
&lt;P&gt;2. we have to reload MnT on 2.4 every month because of a current bug on 2.4, will there be any potential effect on licenses if the reload is done on MnT during transition period.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 14:59:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627958#M575320</guid>
      <dc:creator>ammahend</dc:creator>
      <dc:date>2022-06-08T14:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE licensing question</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627973#M575321</link>
      <description>&lt;P&gt;Assuming your traditional licenses are PAK, and the 2.4 deployment is not using smart licensing, then those licenses will be unaffected. The 2.4 deployment will be unaware of any licensing changes you're making in the smart account or in preparation for 3.x.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#2, reloading the MNT, this will be fine, the 2.4 deployment will run as it always has for you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 15:18:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627973#M575321</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2022-06-08T15:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: ISE licensing question</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627975#M575322</link>
      <description>&lt;P&gt;Thanks Damien, yes it is PAK, that's what I thought but certainly doesn't hurt to have a second opinion.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 15:19:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-licensing-question/m-p/4627975#M575322</guid>
      <dc:creator>ammahend</dc:creator>
      <dc:date>2022-06-08T15:19:54Z</dc:date>
    </item>
  </channel>
</rss>

