11-27-2025 12:35 AM
Hi All,
I have a 2-node deployment:
Node A – Admin (Primary), MnT (Primary), PSN
Node B – Admin (Secondary), MnT (Secondary), PSN
After migrating Node B to another site, we changed its IP address and then deregistered it from Node A. However, Node B is still showing as a secondary node. I was expecting it to become standalone. Could you advise how I can change Node B to standalone so that I can change the certeficate and DNS also and register again?
Thanks
11-27-2025 12:54 AM
@henokk60 hi, what is your ISE version? i found this guide for this kind of scenarios.
Solved: forcing ISE node to standalone - Cisco Community
if its not working, you may do the factory reset for Node B.
11-27-2025 01:10 PM
1st deregister the Node B from the Cluster (at Administration > System > Deployment > select Node B and click Deregister)
2nd migrate Node B to another Site, changing its IP Address during the process
3rd register Node B again to Node A's Cluster
About " ... how I can change Node B to Standalone ... ", if Node B was properly deregister, you are able to change the Certificate and DNS.
About " ... Node B is still showing as a Secondary Node ... ", do you mean that you are able to see Node B on Node A's Cluster ?
Note: please take a look at: ISE - What we need to know about DNS Server
Hope this helps !
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide