<?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: Performing ISE Database synchup in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535770#M537930</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Timothy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was still stuck this morning, so reloaded the node and it finished the restore. Probably not recommended, but we are not in production yet with it, so took the risk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Aug 2016 15:52:24 GMT</pubDate>
    <dc:creator>Dustin Anderson</dc:creator>
    <dc:date>2016-08-17T15:52:24Z</dc:date>
    <item>
      <title>Performing ISE Database synchup</title>
      <link>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535768#M537924</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Long story short, we found a bug with trying to use 2 MDM's in ISE 2.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Through trial and error we found the bug, but now I can not get the ISE to use even one MDM. Rebooting did not work, so decided to restore back to Saturday's backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's now been sitting at 80% Performing ISE Database synchup for about 2 hours. I can't log into the web portal until it completes. Does anyone know how to tell if it is stuck, or if there is a way to stop it? I don't want to try to reload in case it just messes it up more.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And from other posts I've seen, system and backup are from 2.1, no patches applied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 23:12:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535768#M537924</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2016-08-16T23:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: Performing ISE Database synchup</title>
      <link>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535769#M537927</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dustin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is still the case, please open a case with the TAC to further troubleshoot the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2016 15:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535769#M537927</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2016-08-17T15:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: Performing ISE Database synchup</title>
      <link>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535770#M537930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Timothy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was still stuck this morning, so reloaded the node and it finished the restore. Probably not recommended, but we are not in production yet with it, so took the risk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2016 15:52:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/performing-ise-database-synchup/m-p/3535770#M537930</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2016-08-17T15:52:24Z</dc:date>
    </item>
  </channel>
</rss>

