<?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: Primary ISE Node failure and replacement. in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3215058#M22786</link>
    <description>&lt;P&gt;Yes, steps 1 and 6 require downtime. ISE services restart at the same time on both nodes.&lt;/P&gt;</description>
    <pubDate>Sat, 11 Nov 2017 22:05:47 GMT</pubDate>
    <dc:creator>Peter Koltl</dc:creator>
    <dc:date>2017-11-11T22:05:47Z</dc:date>
    <item>
      <title>Primary ISE Node failure and replacement.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3034829#M22773</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a two node ISE Virtual appliance setup.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Node 1 - Primary Admin Role, Primary Monitoring Role, PSN&lt;/P&gt;
&lt;P&gt;Node 2 - Secondary Admin Role, Secondary Monitoring Role, PSN&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Node 1 failed recently and needs to be recreated. Needed help to establish step-by-step procedure for getting the node 1 back in service.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Planned Approach -&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;1. Promote Node 2 as Primary Admin and Monitoring.&lt;/P&gt;
&lt;P&gt;2. De-register failed Node 1 from the now Primary Admin Node (Node 2).&lt;/P&gt;
&lt;P&gt;3. Setup new Node 1 with all patches, certificate, etc.&lt;/P&gt;
&lt;P&gt;4.&amp;nbsp;Restore operational backup on the new standalone node 1.&lt;/P&gt;
&lt;P&gt;5. Add new node (Node 1) as secondary ISE node.&lt;/P&gt;
&lt;P&gt;6. Promote Node 1 as primary Admin and Monitoring.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Is this approach ok or do i need to make any changes to it to ensure node 1 is put back in service with the current configuration and old log data.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rgds,&lt;/P&gt;
&lt;P&gt;Aniket Alashe&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:43:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3034829#M22773</guid>
      <dc:creator>aniketalashe</dc:creator>
      <dc:date>2019-03-11T07:43:51Z</dc:date>
    </item>
    <item>
      <title>You can skip step 4.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3034830#M22778</link>
      <description>&lt;P&gt;You can skip step 4.&lt;/P&gt;
&lt;P&gt;Your step 5 will replicate all of the policy and other configuration bits (including MnT logs up to the current time) that need to be synchronized for the deployment from Node 2.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 20 May 2017 14:35:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3034830#M22778</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-05-20T14:35:44Z</dc:date>
    </item>
    <item>
      <title>Hello Marvin,</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3034831#M22780</link>
      <description>&lt;P&gt;Hello Marvin,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for your help, but I had already performed the mentioned steps and the new node is back in service with all configuration and log data.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks once again for your valuable inputs.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rgds,&lt;/P&gt;
&lt;P&gt;Aniket Alashe&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2017 06:07:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3034831#M22780</guid>
      <dc:creator>aniketalashe</dc:creator>
      <dc:date>2017-05-21T06:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: Primary ISE Node failure and replacement.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3204066#M22783</link>
      <description>&lt;P&gt;Do&amp;nbsp;Steps 1 and 6 require downtime? Will&amp;nbsp;services be running all the time at least on Node 2? Or do the ISE&amp;nbsp;(PSN)&amp;nbsp;services restart during&amp;nbsp;the promotion?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Oct 2017 08:46:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3204066#M22783</guid>
      <dc:creator>Peter Koltl</dc:creator>
      <dc:date>2017-10-24T08:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Primary ISE Node failure and replacement.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3215058#M22786</link>
      <description>&lt;P&gt;Yes, steps 1 and 6 require downtime. ISE services restart at the same time on both nodes.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2017 22:05:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3215058#M22786</guid>
      <dc:creator>Peter Koltl</dc:creator>
      <dc:date>2017-11-11T22:05:47Z</dc:date>
    </item>
    <item>
      <title>Re: You can skip step 4.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3331209#M22789</link>
      <description>&lt;P&gt;are you sure about automatic replication of MNT logs?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 19:03:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3331209#M22789</guid>
      <dc:creator>Dev Vishwakarma</dc:creator>
      <dc:date>2018-02-14T19:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: You can skip step 4.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3735615#M22790</link>
      <description>&lt;P&gt;&lt;SPAN class="short_text"&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="short_text"&gt;&lt;SPAN&gt;Do we have an answer for this?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="short_text"&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Oct 2018 13:58:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3735615#M22790</guid>
      <dc:creator>daniel.landry</dc:creator>
      <dc:date>2018-10-30T13:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: You can skip step 4.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3735757#M22791</link>
      <description>&lt;P&gt;If the replacement ISE node is to act as MNT and if it needs to report on historical data, then please restore the latest backup or take a new backup of OPS data and restore to the new ISE node.&lt;/P&gt;
&lt;P&gt;That is, the historical data can only be restored by backup and restore of OPS data; the new events will send to the new ISE node once it registered with MNT persona.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Oct 2018 16:44:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/3735757#M22791</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-10-30T16:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: You can skip step 4.</title>
      <link>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/4917475#M583899</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I am also facing the same issue, with the only difference being that the node to be replaced is on a physical appliance and the secondary one is on a virtual one. I wonder if the approach remains the same."&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2023 17:51:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/primary-ise-node-failure-and-replacement/m-p/4917475#M583899</guid>
      <dc:creator>Arsene ALLOGO</dc:creator>
      <dc:date>2023-09-04T17:51:38Z</dc:date>
    </item>
  </channel>
</rss>

