<?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 cluster upgrade in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123418#M589806</link>
    <description>&lt;P&gt;Huh?&amp;nbsp; This is not a supported deployment type.&amp;nbsp; How many nodes total?&amp;nbsp; Three?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/performance_and_scalability/b_ise_perf_and_scale.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/performance_and_scalability/b_ise_perf_and_scale.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 03 Jun 2024 14:00:18 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2024-06-03T14:00:18Z</dc:date>
    <item>
      <title>ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119494#M589693</link>
      <description>&lt;P&gt;ISE nodes in DC and DR plus a monitoring node. DC &amp;amp; DR node runs admin, policy service in single node. Currently version 3.2, what's the procedure to upgrade to 3.3 in this scenario.&amp;nbsp;&lt;BR /&gt;Should we upgrade node one-by-one.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 12:59:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119494#M589693</guid>
      <dc:creator>manvik</dc:creator>
      <dc:date>2024-05-29T12:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119738#M589699</link>
      <description>&lt;P&gt;There are a number of steps required for an ISE upgrade and it really depends on your node setup.&lt;/P&gt;&lt;P&gt;If you have a look at this guide:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-3/upgrade_guide/Upgrade_Journey/PDF/b_ise_upgrade_guide_3_3_pdf.pdf" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/3-3/upgrade_guide/Upgrade_Journey/PDF/b_ise_upgrade_guide_3_3_pdf.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Starting on page 21 it will go over the process and it has the upgrade order for all different types of deployment, just choose the one that matches your setup and follow that.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 16:02:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119738#M589699</guid>
      <dc:creator>Ben Walters</dc:creator>
      <dc:date>2024-05-29T16:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119808#M589700</link>
      <description>&lt;P&gt;What type of deployment is this?&amp;nbsp; Small medium or large?&amp;nbsp; It sounds to me like this is not supported deployment.&amp;nbsp; What roles are on each node?&amp;nbsp; How many nodes?&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 16:59:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119808#M589700</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-05-29T16:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119983#M589703</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/161770"&gt;@manvik&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;1st&lt;/STRONG&gt;&amp;nbsp;to get the software: &lt;A href="https://cs.co/ise-software" target="_blank" rel="noopener"&gt;ISE Software Download&lt;/A&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;2nd&amp;nbsp;&lt;/STRONG&gt;check your &lt;STRONG&gt;ISE 3.2 Patch&lt;/STRONG&gt; number ... remember that &lt;STRONG&gt;ISE 3.3&lt;/STRONG&gt; has parity with &lt;STRONG&gt;ISE 3.2 Patch 2&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;3rd&lt;/STRONG&gt;&amp;nbsp;you will upgrade your &lt;STRONG&gt;ISE Cluster&lt;/STRONG&gt; first to &lt;STRONG&gt;ISE 3.3&lt;/STRONG&gt; and next to &lt;STRONG&gt;ISE 3.3 Patch 2&lt;/STRONG&gt; (the latest version of &lt;STRONG&gt;ISE 3.3&lt;/STRONG&gt;)&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;4th&lt;/STRONG&gt;&amp;nbsp;use the &lt;STRONG&gt;URT (Upgrade Readiness Tool)&lt;/STRONG&gt; to validate &lt;STRONG&gt;Config DB&lt;/STRONG&gt; upgrade from &lt;STRONG&gt;3.2&lt;/STRONG&gt; to &lt;STRONG&gt;3.3&lt;/STRONG&gt;&amp;nbsp;(file&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;ise-urtbundle-3.3.0.430a-1.0.0.SPA.x86_64.tar.gz&lt;/STRONG&gt;)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;SPAN&gt;&lt;STRONG&gt;5th&lt;/STRONG&gt; you can upgrade via &lt;STRONG&gt;CLI&lt;/STRONG&gt; or &lt;STRONG&gt;GUI&lt;/STRONG&gt; (check the &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-3/upgrade_guide/Upgrade_Journey/Cisco_ISE_3-3_Upgrade_Journey.html" target="_blank" rel="noopener"&gt;Cisco ISE Journey for Release 3.3&lt;/A&gt;) and choose your &lt;U&gt;upgrade sequence&lt;/U&gt; of the &lt;STRONG&gt;Nodes&lt;/STRONG&gt;, please take a look at:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ISE Upgrade Journey 3.3.png" style="width: 863px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/219555i95E1F45DE6CAA559/image-dimensions/863x480?v=v2" width="863" height="480" role="button" title="ISE Upgrade Journey 3.3.png" alt="ISE Upgrade Journey 3.3.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 20:48:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5119983#M589703</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2024-05-29T20:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123113#M589786</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;it's a small deployment. Each ISE VM has policy, admin node. ISE used only for Tacacs authentication. The tac says upgrade can be done from ISE 3.2 to 3.3.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 04:53:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123113#M589786</guid>
      <dc:creator>manvik</dc:creator>
      <dc:date>2024-06-03T04:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123172#M589789</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/17232"&gt;@Marcelo Morais&lt;/a&gt;&amp;nbsp; and &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/449686"&gt;@Ben Walters&lt;/a&gt;&amp;nbsp;the TAC says upgrade can directly be done to version 3.3. I am planning to do so.&lt;BR /&gt;Most of the ISE upgrade documents were mentioning to detach ISE node from cluster before upgrade, then perform upgrade.&lt;BR /&gt;I understand it's not required. If upgrading OS first upgrade secondary ISE VM, then primary.&amp;nbsp;&lt;BR /&gt;If upgrading patch first primary then secondary ISE VM.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 07:06:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123172#M589789</guid>
      <dc:creator>manvik</dc:creator>
      <dc:date>2024-06-03T07:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123378#M589796</link>
      <description>&lt;P&gt;Got it, so only two nodes then?&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 12:12:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123378#M589796</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-06-03T12:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123415#M589805</link>
      <description>&lt;P&gt;Yes, two nodes + one for dedicated monitoring (MnT).&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 13:53:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123415#M589805</guid>
      <dc:creator>manvik</dc:creator>
      <dc:date>2024-06-03T13:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123418#M589806</link>
      <description>&lt;P&gt;Huh?&amp;nbsp; This is not a supported deployment type.&amp;nbsp; How many nodes total?&amp;nbsp; Three?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/performance_and_scalability/b_ise_perf_and_scale.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/performance_and_scalability/b_ise_perf_and_scale.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 14:00:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123418#M589806</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-06-03T14:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123456#M589807</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/161770"&gt;@manvik&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;if you "detach" &lt;STRONG&gt;ISE Node&lt;/STRONG&gt; (de-register the &lt;STRONG&gt;Secondary Node&lt;/STRONG&gt; from &lt;STRONG&gt;Primary&lt;/STRONG&gt;), your &lt;STRONG&gt;Small Deployment&lt;/STRONG&gt; will become two &lt;STRONG&gt;Standalone Deployment&lt;/STRONG&gt;., after that you are able to upgrade one &lt;STRONG&gt;Standalone Deployment&lt;/STRONG&gt; to &lt;STRONG&gt;ISE 3.3 Patch 2&lt;/STRONG&gt; and double check if everything is fine before upgrade the other &lt;STRONG&gt;Standalone Deployment&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 15:01:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-upgrade/m-p/5123456#M589807</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2024-06-03T15:01:42Z</dc:date>
    </item>
  </channel>
</rss>

