<?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 3.3 stability in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985963#M585900</link>
    <description>&lt;P&gt;Since 3.3 isnt the go to yet, we'll definitely go to 3.2.&amp;nbsp; &amp;nbsp;Plus I'd rather not have to upgrade twice to get to 3.3.&amp;nbsp; &amp;nbsp;and yes, I have dont talked to Cisco TAC about the license.&amp;nbsp; &amp;nbsp;They recommended to upgrade the license after the upgrade in case the upgrade goes sideways and need to revert back because once the license is converted, it cant be converted back.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Dec 2023 14:40:30 GMT</pubDate>
    <dc:creator>dropped_packetz</dc:creator>
    <dc:date>2023-12-27T14:40:30Z</dc:date>
    <item>
      <title>ISE 3.3 stability</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985318#M585888</link>
      <description>&lt;P&gt;I need to start working on a game plan to upgrade our 6-node ISE cluster which is currently on 2.7.&amp;nbsp; &amp;nbsp;Is Ver 3.3 stable enough for production yet?&amp;nbsp; &amp;nbsp;Or would it still be best to go with 3.2 at this point?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Dec 2023 22:20:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985318#M585888</guid>
      <dc:creator>dropped_packetz</dc:creator>
      <dc:date>2023-12-26T22:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.3 stability</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985332#M585892</link>
      <description>&lt;P&gt;My two cent, usually with any new version I would wait for 1st patch at least which is available in 3.3, having said that unless you need a &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-3/release_notes/b_ise_33_RN.html#concept_qym_txq_4sb" target="_self"&gt;feature&lt;/A&gt; introduced in 3.3 its better to stay with 3.2 with latest patch.&lt;/P&gt;
&lt;P&gt;I am assuming you are aware of prerequisites for licenses and node from 2.7 to 3.X while considering your upgrade, if not read &lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/ise-licensing-guide-og.html" target="_self"&gt;here&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Dec 2023 00:34:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985332#M585892</guid>
      <dc:creator>Ambuj M</dc:creator>
      <dc:date>2023-12-27T00:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.3 stability</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985963#M585900</link>
      <description>&lt;P&gt;Since 3.3 isnt the go to yet, we'll definitely go to 3.2.&amp;nbsp; &amp;nbsp;Plus I'd rather not have to upgrade twice to get to 3.3.&amp;nbsp; &amp;nbsp;and yes, I have dont talked to Cisco TAC about the license.&amp;nbsp; &amp;nbsp;They recommended to upgrade the license after the upgrade in case the upgrade goes sideways and need to revert back because once the license is converted, it cant be converted back.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Dec 2023 14:40:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-3-stability/m-p/4985963#M585900</guid>
      <dc:creator>dropped_packetz</dc:creator>
      <dc:date>2023-12-27T14:40:30Z</dc:date>
    </item>
  </channel>
</rss>

