Home » Security » [solved] how to fix the Cisco ISE application server stuck in initializing mode step by step

[solved] how to fix the Cisco ISE application server stuck in initializing mode step by step

How to fix the Cisco ISE application server stuck in the initializing mode. In this case the roles were split into different virtual machines and the application server on the ISE administration node went into the initialization mode.

You can see the below by using the “sh application status ise” .

In this case the administration page was not loading, however all authentications were working since the policy node was installed on a separate virtual machine.  that is the benefit of all having to split the roles. It splits the load between all ISE nodes and improves performance.

One thing to note that you will need to call Cisco support for root login in order to check the logs to see what may be causing the application server to crash.

Now you will need to run the command “application stop ise” to stop the application gracefully

Once the application server is fully stopped then it can be rebooted to by using the “reload” command

The application will be in a running state after the reload

Now the server is up there are few things that can be done to find the root cause

Here is how to collect a support bundle to check why the services is not responding and the application server was stuck in the initialization mode

    1. Navigate to Operations > Troubleshoot > Download logs. Select the node on which the logs should be collected.

    2. The support bundle can be found under: Operations > Troubleshoot > Download Logs > [select node]

 

         Please generate the file using the following options:

 

         [ ] Include full configuration database

         [x] Include debug logs

         [x] Include local logs

         [x] Include core files

         [x] Include monitoring and reporting logs

         [x] Include system logs

         [x] Include policy configuration 

        

         Set the encryption key to: Appserverissue

 

         Select the (time range)days on which the issue happened. this is an estimate where you think the issue started 

        below is the what it looks like and the options, you do not need to choose the configurations database and policy configurations

This is what can be submitted to Cisco support for more analysis

 

Thanks for reading this and I hope it helps

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*