<?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 background upgrades using vmware features in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-background-upgrades-using-vmware-features/m-p/3177720#M553934</link>
    <description>&lt;P&gt;You could perform ISE application backup of the current environment, build a new 2.3 environment and restore the backup. I believe&amp;nbsp;using VMware snapshots is not supported.&amp;nbsp;I think the tricky part of doing upgrade this way would be the point when you need to make to new system live. You need to make sure you test the new environment properly.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Aug 2017 08:47:09 GMT</pubDate>
    <dc:creator>agrissimanis</dc:creator>
    <dc:date>2017-08-30T08:47:09Z</dc:date>
    <item>
      <title>ISE background upgrades using vmware features</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-background-upgrades-using-vmware-features/m-p/3177122#M553927</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; - ISE is business critical in our environment as it determines network access both for wired and wireless; we are currently running 2.2 - P1. I don't want to upgrade the production environment to P2 or 2.3 even if can be done in seperate steps (per node). We have 2 admin/mon and 2 PSN nodes. Ideally I would like to start from snapshots from the current production nodes and create a new deployment which I could then upgrade, while the production environment isn't disturbed. Is this possible or flexible; did anyone do it that way already and or has guidelines ?&lt;/P&gt;&lt;P&gt;M.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:33:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-background-upgrades-using-vmware-features/m-p/3177122#M553927</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2020-02-21T18:33:03Z</dc:date>
    </item>
    <item>
      <title>Re: ISE background upgrades using vmware features</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-background-upgrades-using-vmware-features/m-p/3177720#M553934</link>
      <description>&lt;P&gt;You could perform ISE application backup of the current environment, build a new 2.3 environment and restore the backup. I believe&amp;nbsp;using VMware snapshots is not supported.&amp;nbsp;I think the tricky part of doing upgrade this way would be the point when you need to make to new system live. You need to make sure you test the new environment properly.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2017 08:47:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-background-upgrades-using-vmware-features/m-p/3177720#M553934</guid>
      <dc:creator>agrissimanis</dc:creator>
      <dc:date>2017-08-30T08:47:09Z</dc:date>
    </item>
  </channel>
</rss>

