<?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 2.4 Primary Admin Node Restore in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998185#M455033</link>
    <description>&lt;P&gt;Thats great, thanks for confirming Damien&lt;/P&gt;</description>
    <pubDate>Thu, 12 Dec 2019 21:48:47 GMT</pubDate>
    <dc:creator>dm2020</dc:creator>
    <dc:date>2019-12-12T21:48:47Z</dc:date>
    <item>
      <title>ISE 2.4 Primary Admin Node Restore</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998106#M455029</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quick question hopefully. In a distributed ISE 2.4 deployment with primary and secondary Admin nodes, MnT nodes etc, if the primary Admin node fails, can we simply promote the secondary admin node to primary, rebuild the failed admin node, join it back to the cluster and then promote back to primary? Is there are need to complete a full restore in this scenario?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 18:53:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998106#M455029</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2019-12-12T18:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Primary Admin Node Restore</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998117#M455031</link>
      <description>Correct, no need to perform a backup/restore operation if you still have a working admin node.  So your process is correct, promoting your secondary to primary and joining a fresh node as secondary admin will work.  One extra step before joining a new PAN is that you will have to "deregister" the failed admin node from the deployment view first, but this only takes a couple minutes and the node doesn't have to be available to complete.</description>
      <pubDate>Thu, 12 Dec 2019 19:38:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998117#M455031</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-12-12T19:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Primary Admin Node Restore</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998185#M455033</link>
      <description>&lt;P&gt;Thats great, thanks for confirming Damien&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 21:48:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-primary-admin-node-restore/m-p/3998185#M455033</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2019-12-12T21:48:47Z</dc:date>
    </item>
  </channel>
</rss>

