<?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 upgrade in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5116041#M589621</link>
    <description>&lt;P&gt;I agree with balaji.bandi.&lt;BR /&gt;&lt;BR /&gt;I used new VMs when I upgraded from 2.7 to 3.2 . That allowed me to set up everything and make sure it was working before the cutover to the new VMs. My deployment has the PSNs behind an F5 load balancer which allowed for an easy cutover consisting of just changing the node members of the various pools we had set up.&lt;/P&gt;</description>
    <pubDate>Fri, 24 May 2024 20:24:19 GMT</pubDate>
    <dc:creator>Chris Terry</dc:creator>
    <dc:date>2024-05-24T20:24:19Z</dc:date>
    <item>
      <title>ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5115257#M589600</link>
      <description>&lt;P&gt;hello&lt;/P&gt;
&lt;P&gt;we have an ISE v2.7 running on a virtual environment&amp;nbsp;&lt;/P&gt;
&lt;P&gt;when running the health check pre upgrade we get an&amp;nbsp; error message on the platform&amp;nbsp;&lt;/P&gt;
&lt;P&gt;attached file shows the error/warning&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Q has anyone seen this before ?&lt;/P&gt;
&lt;P&gt;I checked the ade logs but did not find any information&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 21:50:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5115257#M589600</guid>
      <dc:creator>stephenstown20</dc:creator>
      <dc:date>2024-05-23T21:50:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5115275#M589602</link>
      <description>&lt;P&gt;What nodes do you have in your deployment? That error almost sounds like you have hybrid deployment of VMs and physical appliances. The physical appliances SNS 3415 and 3495 do not support ISE version past 2.3.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 22:30:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5115275#M589602</guid>
      <dc:creator>Chris Terry</dc:creator>
      <dc:date>2024-05-23T22:30:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5115388#M589609</link>
      <description>&lt;LI-CODE lang="markup"&gt;we have an ISE v2.7 running on a virtual environment &lt;/LI-CODE&gt;
&lt;P&gt;what version you trying to upgrade this Virtual ISE ?&lt;/P&gt;
&lt;P&gt;check the upgrade guide :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/upgrade_guide/HTML/b_upgrade_method_3_1.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/upgrade_guide/HTML/b_upgrade_method_3_1.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you upgrading to 3.X or above i suggest to install fresh ISE is good option.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2024 06:23:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5115388#M589609</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2024-05-24T06:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5116041#M589621</link>
      <description>&lt;P&gt;I agree with balaji.bandi.&lt;BR /&gt;&lt;BR /&gt;I used new VMs when I upgraded from 2.7 to 3.2 . That allowed me to set up everything and make sure it was working before the cutover to the new VMs. My deployment has the PSNs behind an F5 load balancer which allowed for an easy cutover consisting of just changing the node members of the various pools we had set up.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2024 20:24:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5116041#M589621</guid>
      <dc:creator>Chris Terry</dc:creator>
      <dc:date>2024-05-24T20:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: ISE upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5117137#M589635</link>
      <description>&lt;P&gt;In addition to the good advice already shared here, please share a redacted "show inventory" cli output for the VM in question.&lt;/P&gt;</description>
      <pubDate>Mon, 27 May 2024 04:06:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade/m-p/5117137#M589635</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2024-05-27T04:06:56Z</dc:date>
    </item>
  </channel>
</rss>

