<?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: Forcing an ISE node into stand alone mode in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021384#M587482</link>
    <description>&lt;P&gt;By default, all nodes are Standalone upon installation.&lt;/P&gt;
&lt;P&gt;Did you restore to only the PAN or all of the nodes? Restoring to each node might be the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2024 16:52:29 GMT</pubDate>
    <dc:creator>thomas</dc:creator>
    <dc:date>2024-02-20T16:52:29Z</dc:date>
    <item>
      <title>Forcing an ISE node into stand alone mode</title>
      <link>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021258#M587473</link>
      <description>&lt;P&gt;I am in the process of standing up 6 new&amp;nbsp;SNS-3755-K9 servers. They are running 3.1 software. I just did a back up/restore on the new environment from our production in order to get a lot of the configuration stuff done. When the nodes came back up I changed the PAN from stand alone to primary. When I tried to register my other 5 nodes I got an error saying "&lt;SPAN&gt;Node is not a Standalone node". All indications are they are stand alones and there is no option in the GUI to make the other 5 stand alone. Do I need to reboot them? Is there an option in CLI&amp;nbsp; to make them stand alone so I can register them?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 13:55:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021258#M587473</guid>
      <dc:creator>pmcternan</dc:creator>
      <dc:date>2024-02-20T13:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: Forcing an ISE node into stand alone mode</title>
      <link>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021384#M587482</link>
      <description>&lt;P&gt;By default, all nodes are Standalone upon installation.&lt;/P&gt;
&lt;P&gt;Did you restore to only the PAN or all of the nodes? Restoring to each node might be the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 16:52:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021384#M587482</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2024-02-20T16:52:29Z</dc:date>
    </item>
    <item>
      <title>Re: Forcing an ISE node into stand alone mode</title>
      <link>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021388#M587483</link>
      <description>&lt;P&gt;I registered all the nodes in the primary PAN's GUI prior to doing a config restore. When I did the restore the primary PAN came back up as a standalone with all the personas. I changed the PAN from stand alone to the primary and then attempted to register the other 5 nodes as MnT's, PSN's and a backup PAN. That's when I received the error from the nodes I am attempting to register:&amp;nbsp;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;Node is not a Standalone node". The problem is I don't have an option to make the other 5 nodes standalones on their GUI as the GUI is very limited in the actions you can take. Do I need to default/restore them from the CLI for each node?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 17:03:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021388#M587483</guid>
      <dc:creator>pmcternan</dc:creator>
      <dc:date>2024-02-20T17:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: Forcing an ISE node into stand alone mode</title>
      <link>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021458#M587487</link>
      <description>&lt;P class="lia-indent-padding-left-30px lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1178373"&gt;@pmcternan&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px lia-align-justify"&gt;&amp;nbsp;&lt;STRONG&gt;1st&lt;/STRONG&gt; remember that you just need to restore the &lt;STRONG&gt;Config Backup&lt;/STRONG&gt; on one &lt;STRONG&gt;Node&lt;/STRONG&gt; (the future &lt;STRONG&gt;Primary PAN&lt;/STRONG&gt;),&amp;nbsp;the others &lt;STRONG&gt;5x Nodes&lt;/STRONG&gt; just need to have a &lt;U&gt;fresh install&lt;/U&gt; (same &lt;STRONG&gt;Version &amp;amp; Patch&lt;/STRONG&gt; of the future &lt;STRONG&gt;Primary PAN&lt;/STRONG&gt;), after that every time you register a new &lt;STRONG&gt;Node&lt;/STRONG&gt; the &lt;STRONG&gt;Primary PAN&lt;/STRONG&gt;&amp;nbsp;configuration will be sync with the new &lt;STRONG&gt;Node&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px lia-align-justify"&gt;&amp;nbsp;&lt;STRONG&gt;2nd &lt;/STRONG&gt;please try&amp;nbsp;the following &lt;STRONG&gt;CLI&lt;/STRONG&gt; on the other &lt;STRONG&gt;Nodes&lt;/STRONG&gt;&lt;/P&gt;
&lt;PRE class="lia-indent-padding-left-30px lia-align-justify"&gt;ise/admin# application reset-config ise&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;This node is part of the deployment. It is recommended you first deregister this node from the deployment before resetting the configuration. Proceed with factory reset? (y/n): &lt;U&gt;&lt;STRONG&gt;Y&lt;/STRONG&gt;&lt;/U&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Leaving currently connected AD domains if any...&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Please rejoin to AD domains from the administrative GUI&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Smart Licensing is Not Enabled. Not possible to Disable.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Retain existing Application server certificates? (y/n): &lt;U&gt;&lt;STRONG&gt;Y&lt;/STRONG&gt;&lt;/U&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Reinitializing local configuration to factory defaults...&lt;BR /&gt;&lt;/EM&gt;...&lt;/PRE&gt;
&lt;P class="lia-indent-padding-left-30px lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 20:15:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021458#M587487</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2024-02-20T20:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Forcing an ISE node into stand alone mode</title>
      <link>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021905#M587502</link>
      <description>&lt;P&gt;Thank You Marcelo. If I reset them from the CLI using the application reset-config ise command will they lose their FQDN, IP address certificate and username and PW? Will I need to console in and redo all of that when it comes back up? Thanks in advance.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2024 14:37:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/forcing-an-ise-node-into-stand-alone-mode/m-p/5021905#M587502</guid>
      <dc:creator>pmcternan</dc:creator>
      <dc:date>2024-02-21T14:37:44Z</dc:date>
    </item>
  </channel>
</rss>

