<?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 Those would work. If you in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051903#M23313</link>
    <description>&lt;P&gt;Those would work. If you build from scratch, you will have to rehost your licenses as the VUDI will change.&lt;/P&gt;
&lt;P&gt;You just don't want to have two VMs with the exact same configuration trying to run at the same time.&lt;/P&gt;</description>
    <pubDate>Fri, 31 Mar 2017 15:47:39 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2017-03-31T15:47:39Z</dc:date>
    <item>
      <title>ISE 2.2 Install Using A ISE 1.4 Backup</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051900#M23309</link>
      <description>&lt;P&gt;Running a 1.4 VM Distributed Deployment with a PAN/Mon, SAN/Mon and two PSNs. I've created new 2.2 Nodes and want to restore from the 1.4 backups. Need to know if this can be done without causing my current PAN/Mon Node to deregister.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:35:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051900#M23309</guid>
      <dc:creator>Henry Sumner</dc:creator>
      <dc:date>2019-03-11T07:35:28Z</dc:date>
    </item>
    <item>
      <title>While resotre from 1.4 onto 2</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051901#M23311</link>
      <description>&lt;P&gt;While restore from 1.4 onto 2.2 is supported (reference below), it would seem to me that you would then have two hosts with the same persona, certificates etc. on your network. That would Not Be Good and would likely lead to unintended consequences.&lt;/P&gt;
&lt;P&gt;Why not follow the recommended inline upgrade path? That tends to work quite well. If you don't want to do that, then I'd take a node offline before restoring its backup to another separate VM.&lt;/P&gt;
&lt;P&gt;Reference:&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/2-2/admin_guide/b_ise_admin_guide_22/b_ise_admin_guide_22_chapter_01011.html#reference_4F69987D3294499E95C1B652C4D1E73D&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 02:48:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051901#M23311</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-03-31T02:48:42Z</dc:date>
    </item>
    <item>
      <title>Marvin,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051902#M23312</link>
      <description>&lt;P&gt;Marvin,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you for the reply. I should have mentioned that because of a network redesign we had to build out the new VMs on different ESX host than the ones in production today that is why we can't do the inline upgrade.&amp;nbsp;I've got two options here that I think will work.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Option 1: Build out the new nodes from scratch. That way I can do some testing before moving them into production. On the day that I'm ready to move into production I'll just &lt;G class="gr_ gr_1174 gr-alert gr_spell gr_run_anim ContextualSpelling" id="1174" data-gr-id="1174"&gt;shutdown&lt;/G&gt; the old nodes. I'll have to change all of my NADs to point to the new IPs but I only have 4 NADs using ISE at this time so that won't be a big deal.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Option 2: During a maintenance window, restore the 1.4 &lt;G class="gr_ gr_1494 gr-alert gr_gramm gr_run_anim Grammar multiReplace" id="1494" data-gr-id="1494"&gt;backup&lt;/G&gt; to the 2.2 nodes. Then &lt;G class="gr_ gr_1510 gr-alert gr_spell gr_run_anim ContextualSpelling" id="1510" data-gr-id="1510"&gt;shutdown&lt;/G&gt; the old nodes.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 11:36:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051902#M23312</guid>
      <dc:creator>Henry Sumner</dc:creator>
      <dc:date>2017-03-31T11:36:19Z</dc:date>
    </item>
    <item>
      <title>Those would work. If you</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051903#M23313</link>
      <description>&lt;P&gt;Those would work. If you build from scratch, you will have to rehost your licenses as the VUDI will change.&lt;/P&gt;
&lt;P&gt;You just don't want to have two VMs with the exact same configuration trying to run at the same time.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 15:47:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-install-using-a-ise-1-4-backup/m-p/3051903#M23313</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-03-31T15:47:39Z</dc:date>
    </item>
  </channel>
</rss>

