03-31-2022 07:36 AM
Due to the current international situation, we as would like to know the consequences or any problems that may arise from an emergency shutdown of CISCO ISE.
I couldn't find anything about this on Cisco's public pages. Can you make a statement in this regard, optimally backed up with documents from Cisco?
As ISE we use the following system - SNS-3655-K9
Solved! Go to Solution.
03-31-2022 08:29 AM
Typically, an ISE node that abruptly loses power and is incorrectly shutdown will boot up correctly after. Like with any computer system, there is always the possibility of corruption due to the timing of writes, but I've seen this many times with only a single failure. In that case I believe it was the external storage that was corrupted and not and issue with ISE itself.
If you gracefully shutdown an ISE node from the CLI with "application stop ise", then the "halt" command, this node will boot up with it's data intact. The only consideration here is that when the node or nodes are brought back online, given certain circumstances such as being offline for over a day, or being more than a million messages behind on replication, then you might have to perform a manual sync up. The process takes about 20-30 minutes, and the node will reboot services, but it will join back with the single "sync up" click in the gui.
If nodes were down for a vey long time then certificates can expire while offline, this would potentially require a larger time investment it get back up and running after a prolonged shutdown.
03-31-2022 08:26 AM
emergency shutdown of CISCO ISE.
just power off ? or admin shutdown ?
Generally most of the system should come up as expected when the Power off unexpectly and auto fix and work normally.
if something gone bad, then re-image required and restore teh backup.
if you do admin shutdown, that is safe way to do so.
Note : again what node you shutdown also important.
03-31-2022 08:29 AM
Typically, an ISE node that abruptly loses power and is incorrectly shutdown will boot up correctly after. Like with any computer system, there is always the possibility of corruption due to the timing of writes, but I've seen this many times with only a single failure. In that case I believe it was the external storage that was corrupted and not and issue with ISE itself.
If you gracefully shutdown an ISE node from the CLI with "application stop ise", then the "halt" command, this node will boot up with it's data intact. The only consideration here is that when the node or nodes are brought back online, given certain circumstances such as being offline for over a day, or being more than a million messages behind on replication, then you might have to perform a manual sync up. The process takes about 20-30 minutes, and the node will reboot services, but it will join back with the single "sync up" click in the gui.
If nodes were down for a vey long time then certificates can expire while offline, this would potentially require a larger time investment it get back up and running after a prolonged shutdown.
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