<?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 Thanks heaps Jatin...I'll try in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990638#M38214</link>
    <description>Thanks heaps Jatin...I'll try it out..will it be the same for Prime Infrastructure as well?</description>
    <pubDate>Thu, 22 Sep 2016 23:27:22 GMT</pubDate>
    <dc:creator>akshay</dc:creator>
    <dc:date>2016-09-22T23:27:22Z</dc:date>
    <item>
      <title>ISE Migration</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990636#M38212</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;
&lt;P&gt;I need to migrate an ISE 1.2 server and Prime server&amp;nbsp;from a company we have acquired to our DC. We intend to use the same IP Addressing scheme. Can you please let me know the best way to do it, without causing too much of an outage?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Akshay&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 00:35:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990636#M38212</guid>
      <dc:creator>akshay</dc:creator>
      <dc:date>2019-03-26T00:35:17Z</dc:date>
    </item>
    <item>
      <title>Akshay,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990637#M38213</link>
      <description>&lt;P&gt;Akshay,&lt;/P&gt;
&lt;P&gt;This section is basically for AAA so I can tell you about ISE essentially you need to grab&lt;/P&gt;
&lt;P&gt;1. The FULL backup from ISE including ADEOS,&lt;/P&gt;
&lt;P&gt;2. Create an ISE instance ( Same code / version ) in your DC with some other IP for time being.&lt;/P&gt;
&lt;P&gt;3. Shutdown the Existing ISE interface ( to avoid the IP conflict) and restore the FULL backup on DC instance. Once restore is done successfully, it will override the IP with the original one.&lt;/P&gt;
&lt;P&gt;Note: The only downtime you will face, when you shutdown the interface and restore is in progress.&lt;/P&gt;
&lt;P&gt;Regards ~ Jatin&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 15:07:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990637#M38213</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2016-09-22T15:07:16Z</dc:date>
    </item>
    <item>
      <title>Thanks heaps Jatin...I'll try</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990638#M38214</link>
      <description>Thanks heaps Jatin...I'll try it out..will it be the same for Prime Infrastructure as well?</description>
      <pubDate>Thu, 22 Sep 2016 23:27:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-migration/m-p/2990638#M38214</guid>
      <dc:creator>akshay</dc:creator>
      <dc:date>2016-09-22T23:27:22Z</dc:date>
    </item>
  </channel>
</rss>

