topic Re: forcing ISE node to standalone in Network Access Control

forcing ISE node to standalone

Joe Rust — Tue, 10 Oct 2017 17:42:01 GMT

I've de-registered an ISE 2.3 node from a deployment, yet the node does not know that it 'should' be in Standalone mode. Is there a cli command to force it into standalone mode?

Re: forcing ISE node to standalone

Arne Bier — Wed, 11 Oct 2017 01:39:15 GMT

No CLI for that, unless you are happy to factory reset the node.

ise01/admin# application reset-config ise

Initialize your Application configuration to factory defaults? (y/n):

You can retain any certs that you installed, but all else gets wiped out, and then you are back to being a STANDALONE node.

Or via the GUI:

If you log into the Web GUI of the de-registered node, then you should see a 'Make STANDALONE' button.

Re: forcing ISE node to standalone

ivy.liao@telus.com — Fri, 07 Jun 2019 21:05:38 GMT

No need to restore factory default but after de-register the other nodes, reboot the PAN and after reboot, click "Make Standalone" button and it will work.

Re: forcing ISE node to standalone

kaveseli — Wed, 22 Dec 2021 18:43:24 GMT

No need for reset-config. You can force it by typing this in the URL field: https://<IP_OF_PSN>/deployment-rpc/deregister-node
You would need to type in your admin credentials.

Re: forcing ISE node to standalone

Amen — Wed, 13 Apr 2022 13:34:12 GMT

Hello, I was about to do that today, but was not sure, is your command to be done from the CLI to the Node to force it to be standalone?? I had to do a factory reset after 1- de-registered the affected Node from the Primary working Node GUI. and then from the CLI tried application reset-config ise, and typed yes to factory default and then yes to factory reset , but showed me after a while an error that it will not work the error was ((( Error: DATABASE PRIMING FAILED!

this could be the result of incorrect network interface configuration, or lack of resources on the appliance or VM. please fix the issue and run the following CLI to re-prime database:

"application reset-config ise" )))

2- tried to reload 2 times but also didn't help

3-I had to do a factory reset for the whole Node.

Re: forcing ISE node to standalone

Marcelo Morais — Wed, 13 Apr 2022 22:18:34 GMT

Hi @Amen ,

if you have database issues that application reset-config ise didn't solve it, then IMO please:

1. de-register the PSN Node from the Cluster (at Administration > System >Deployment > select the PSN Node > click Deregister.

2. rebuild the PSN Node (from step 1.) from scratch

3. register the PSN Node (from step 2.) to the Cluster

Hope this helps !!!

Re: forcing ISE node to standalone

jbowling723 — Tue, 11 Jun 2024 14:50:21 GMT

That worked perfectly!

Re: forcing ISE node to standalone

Nathan E — Wed, 12 Feb 2025 20:16:27 GMT

You're awesome. This worked for me. For anyone else, this page may load for a few minutes but it will work. The ISE application will also go down for a few minutes and restart.