<?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 registering a node in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987610#M455573</link>
    <description>&lt;P&gt;Yes good catch, So once i rebuild the Primary PAN il have to re-host the APEX and PLUS licensing ? And probably the VM licensing ..?&lt;/P&gt;</description>
    <pubDate>Fri, 22 Nov 2019 00:47:46 GMT</pubDate>
    <dc:creator>x00008037</dc:creator>
    <dc:date>2019-11-22T00:47:46Z</dc:date>
    <item>
      <title>ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987129#M455497</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wondering if anyone have had issue with doing the following:&lt;/P&gt;&lt;P&gt;I have two ISE Admin nodes one pri and one secondary which have been deployed with really low unsupported vm specs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;My plan is to remove the secondary Admin role from the production secondary PAN.&lt;/LI&gt;&lt;LI&gt;Build a new shiny ISE Admin node with the correct vm spec (reservations,ram,shares,HD,CPU etc..)&lt;/LI&gt;&lt;LI&gt;Register the new VM as a secondary Admin node&lt;UL&gt;&lt;LI&gt;Will there be DB sync issues as HD sizes do not match on both nodes?&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Promote the Secondary to Primary and deregister the original primary PAN&lt;/LI&gt;&lt;LI&gt;Build another shiny ISE Admin node with the correct vm spec (reservations,ram,shares,HD,CPU etc..)&lt;/LI&gt;&lt;LI&gt;Register this node as Secondary Admin Node&lt;/LI&gt;&lt;LI&gt;Promote to Primary.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Anyone see any issues?&lt;/P&gt;&lt;P&gt;im thinking this is standard but I want to double check as Admin node holds all the goodness in an ISE deploy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 21 Nov 2019 09:29:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987129#M455497</guid>
      <dc:creator>x00008037</dc:creator>
      <dc:date>2019-11-21T09:29:28Z</dc:date>
    </item>
    <item>
      <title>Re: ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987284#M455498</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/382717"&gt;@x00008037&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I really don't see any issues with different specs causing replication problems.&lt;/P&gt;
&lt;P&gt;One catch - It's have to be same version (and same patch level) as the Primary.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 15:14:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987284#M455498</guid>
      <dc:creator>Anurag Sharma</dc:creator>
      <dc:date>2019-11-21T15:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987544#M455499</link>
      <description>&lt;P&gt;In addition to what&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/223750"&gt;@Anurag Sharma&lt;/a&gt;&amp;nbsp; said, also consider that the UDI's of both nodes will change - unless you're using Cisco Smart Licencing, you'll have to re-home all your licenses with the new UDI information. Apart from the other stuff like re-joing AD etc. Usual upgrade scenario.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 22:21:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987544#M455499</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-11-21T22:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987609#M455500</link>
      <description>&lt;P&gt;Cheers Anurag, Yes all on same patch and veriosn&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 00:46:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987609#M455500</guid>
      <dc:creator>x00008037</dc:creator>
      <dc:date>2019-11-22T00:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987610#M455573</link>
      <description>&lt;P&gt;Yes good catch, So once i rebuild the Primary PAN il have to re-host the APEX and PLUS licensing ? And probably the VM licensing ..?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 00:47:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987610#M455573</guid>
      <dc:creator>x00008037</dc:creator>
      <dc:date>2019-11-22T00:47:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987611#M455575</link>
      <description>&lt;P&gt;Actually i think it will just be the VM licensing ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any thought?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 00:48:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987611#M455575</guid>
      <dc:creator>x00008037</dc:creator>
      <dc:date>2019-11-22T00:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: ISE registering a node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987621#M455577</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/382717"&gt;@x00008037&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Every ISE Traditional License has the UDI baked into the .lic file - this includes Base, Plus, Apex, Device Admin and VM. You have to re-home everything.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With Smart Licensing you wouldn't have this headache. The only requirement would be to enable Smart Licensing with a valid token and off it goes. It's a great feature if you have the opportunity to use it.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 01:16:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-registering-a-node/m-p/3987621#M455577</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-11-22T01:16:06Z</dc:date>
    </item>
  </channel>
</rss>

