<?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 ISE Primary Node Rebuild in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785583#M486013</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a single PAN/MnT node and two distributed PSN nodes. The version of the deployment is 2.3. I'm not sure why we have a single PAN but it needs to be rebuilt&amp;nbsp;as it was under spec'd.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to workout the best way to rebuild the PAN and if its a simple matter of building a new PAN/MnT node, backing up and restoring the config from the old PAN to the new&amp;nbsp;PAN&amp;nbsp;and then switching off the old node. I will then need to change the IP address of the new PAN/MnT to that of the original. Will this work ok? Will the&amp;nbsp;PSNs be able to sync with the new PAN with this procedure?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A possible alternative solution is to build the new node, add it to the cluster as a secondary admin/MnT node, promote it to primary and then demote/decommission the old node. Will this be a better option?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks all&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jan 2019 23:32:46 GMT</pubDate>
    <dc:creator>dm2020</dc:creator>
    <dc:date>2019-01-22T23:32:46Z</dc:date>
    <item>
      <title>ISE Primary Node Rebuild</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785583#M486013</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a single PAN/MnT node and two distributed PSN nodes. The version of the deployment is 2.3. I'm not sure why we have a single PAN but it needs to be rebuilt&amp;nbsp;as it was under spec'd.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to workout the best way to rebuild the PAN and if its a simple matter of building a new PAN/MnT node, backing up and restoring the config from the old PAN to the new&amp;nbsp;PAN&amp;nbsp;and then switching off the old node. I will then need to change the IP address of the new PAN/MnT to that of the original. Will this work ok? Will the&amp;nbsp;PSNs be able to sync with the new PAN with this procedure?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A possible alternative solution is to build the new node, add it to the cluster as a secondary admin/MnT node, promote it to primary and then demote/decommission the old node. Will this be a better option?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks all&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jan 2019 23:32:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785583#M486013</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2019-01-22T23:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Primary Node Rebuild</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785607#M486014</link>
      <description>If I was going to do this, I  would do what you have at the bottom of your post.  Build a new node, join it to the deployment as secondary, promote it to primary, decommission the old pan. &lt;BR /&gt;&lt;BR /&gt;Re-deploy/rebuild the original PAN, promote it to primary, keep the second PAN/MNT for HA.</description>
      <pubDate>Wed, 23 Jan 2019 01:17:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785607#M486014</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-01-23T01:17:57Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Primary Node Rebuild</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785673#M486023</link>
      <description>&lt;P&gt;Damien suggested it right. Also, dont forget to backup the data.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 04:21:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785673#M486023</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2019-01-23T04:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Primary Node Rebuild</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785694#M486026</link>
      <description>I agree on 2nd option. Rebuild as sec then promote as primary.&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Jan 2019 05:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-primary-node-rebuild/m-p/3785694#M486026</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2019-01-23T05:12:04Z</dc:date>
    </item>
  </channel>
</rss>

