<?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: Upgrade the ISE on 2 nodes (active/stand by) in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319292#M566621</link>
    <description>&lt;P&gt;You could do it with minimal downtime, but I wouldn't say zero downtime.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Assuming you upgrade the secondary and that goes well, it becomes the new 2.7 primary. Then you will upgrade the old 2.3 primary to be the 2.7 secondary, this upgrade process in itself is essentially downtime free from an end user perspective. The downtime will come when you want to swap the primary and secondary PAN rolls back to their original positions, both nodes will reload and you'll have about a 10 minute outage during the PAN swap.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Apr 2021 13:25:38 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2021-04-06T13:25:38Z</dc:date>
    <item>
      <title>Upgrade the ISE on 2 nodes (active/stand by)</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319196#M566617</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've the plan to upgrade ISE from 2.3 to 2.7 from my 2 nodes VM (active/standby).&lt;/P&gt;&lt;P&gt;Could you please advise can I do it without the downtime?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 10:27:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319196#M566617</guid>
      <dc:creator>msompong1</dc:creator>
      <dc:date>2021-04-06T10:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade the ISE on 2 nodes (active/stand by)</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319239#M566619</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi,&lt;/P&gt;&lt;P class="lia-align-justify"&gt;&amp;nbsp;take a look at the following link: &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-7/upgrade_guide/Upgrade_Journey/Cisco_ISE_2_7_Upgrade_Journey.html" target="_blank" rel="noopener"&gt;ISE Upgrade Journey, Release 2.7&lt;/A&gt;. and &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-7/compatibility_doc/b_ise_sdt_27.html" target="_blank" rel="noopener"&gt;ISE Compatibility Matrix for 2.7&lt;/A&gt;.&lt;/P&gt;&lt;P class="lia-align-justify"&gt;Have the following in mind to better understand your downtime:&lt;/P&gt;&lt;P class="lia-align-justify"&gt;1. &lt;STRONG&gt;RHEL&lt;/STRONG&gt; for &lt;STRONG&gt;2.3&lt;/STRONG&gt; is &lt;STRONG&gt;7.0&lt;/STRONG&gt;, for &lt;STRONG&gt;2.7&lt;/STRONG&gt; is &lt;STRONG&gt;7.6&lt;/STRONG&gt;. (more time for the upgrade process)&lt;/P&gt;&lt;P class="lia-align-justify"&gt;2. &lt;STRONG&gt;ISE 2.7&lt;/STRONG&gt; supports the following &lt;STRONG&gt;Hardware Platform&lt;/STRONG&gt;: &lt;STRONG&gt;35XX&lt;/STRONG&gt; and &lt;STRONG&gt;36XX&lt;/STRONG&gt; (double check the &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-7/InstallGuide27/b_ise_InstallationGuide27/b_ise_InstallationGuide27_chapter_01.html#ID-1417-00000074" target="_blank" rel="noopener"&gt;VM Appliance Recommendation&lt;/A&gt;, maybe&amp;nbsp; you need to add extra &lt;STRONG&gt;CPU&lt;/STRONG&gt;, &lt;STRONG&gt;Memory&lt;/STRONG&gt; or &lt;STRONG&gt;HDD&lt;/STRONG&gt;)&lt;/P&gt;&lt;P class="lia-align-justify"&gt;3. run the &lt;STRONG&gt;URT&lt;/STRONG&gt; (&lt;EM&gt;Upgrade Readiness Tool&lt;/EM&gt;) before the upgrade to identity any issue that might cause an upgrade failure.&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;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 12:00:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319239#M566619</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2021-04-06T12:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade the ISE on 2 nodes (active/stand by)</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319292#M566621</link>
      <description>&lt;P&gt;You could do it with minimal downtime, but I wouldn't say zero downtime.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Assuming you upgrade the secondary and that goes well, it becomes the new 2.7 primary. Then you will upgrade the old 2.3 primary to be the 2.7 secondary, this upgrade process in itself is essentially downtime free from an end user perspective. The downtime will come when you want to swap the primary and secondary PAN rolls back to their original positions, both nodes will reload and you'll have about a 10 minute outage during the PAN swap.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 13:25:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4319292#M566621</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2021-04-06T13:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade the ISE on 2 nodes (active/stand by)</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4320300#M566655</link>
      <description>&lt;P&gt;Thank you Damien,&lt;/P&gt;&lt;P&gt;So during the upgrade not require the de-register the node right?&lt;/P&gt;&lt;P&gt;Can I say it like this?&lt;/P&gt;&lt;P&gt;1.Backup the config and operation data on the primary node.&lt;BR /&gt;2.Run the URT on the secondary node&lt;BR /&gt;&amp;nbsp; &amp;nbsp; if it passes then&lt;BR /&gt;3.Upgrade to 2.7 from secondary node with CLI&lt;BR /&gt;4.Patch the upgrade in the secondary node to the latest patch version.&lt;BR /&gt;5.Re-do the step 3 and 4 on the primary node.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 04:32:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4320300#M566655</guid>
      <dc:creator>msompong1</dc:creator>
      <dc:date>2021-04-08T04:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade the ISE on 2 nodes (active/stand by)</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4320301#M566656</link>
      <description>&lt;P&gt;Thank you Marcelo for the good information.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 04:32:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-the-ise-on-2-nodes-active-stand-by/m-p/4320301#M566656</guid>
      <dc:creator>msompong1</dc:creator>
      <dc:date>2021-04-08T04:32:58Z</dc:date>
    </item>
  </channel>
</rss>

