06-19-2019 05:00 AM
We have a distributed setup running 2.4 patch 7. We ran into some problems and now one of our PSNs can't start its ISE application services. While we troubleshoot and give it CPR, how long can the PSN be out of the cluster before it needs to be rebuilt and rejoined as a fresh node?
Solved! Go to Solution.
06-19-2019 09:19 AM - edited 06-19-2019 09:20 AM
A node will have to be resynced via the "syncup" button from the deployment view if you hit 1,000,000 records pending replication, it will show replication stopped. I'm not aware if there is a time associated with this as I have always hit the messages pending replication cutoff.
Edit: with the others, if the application service won't startup you probably have a larger issue with the node.
06-19-2019 06:02 AM
06-19-2019 08:40 AM
06-19-2019 09:19 AM - edited 06-19-2019 09:20 AM
A node will have to be resynced via the "syncup" button from the deployment view if you hit 1,000,000 records pending replication, it will show replication stopped. I'm not aware if there is a time associated with this as I have always hit the messages pending replication cutoff.
Edit: with the others, if the application service won't startup you probably have a larger issue with the node.
07-31-2019 03:40 PM
Thank you, the PSN was offline for over a month and we were able to bring the services up and sync it to the cluster again with 700,000 pending records.
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