Cisco ISE 2.0.1.130: Application Server stuck in "initializing" state

[Nashja]

Cisco ISE model: SNS-3415-M-ISE-K9

Cisco version: 2.0.1.130

I tried to fresh setup Cisco ISE. After I input the information such as IP Address, Gateway, NTP and so on, the server started to setup all database.

After that I found the error message that show the database setup error. So, I tried to use command “application reset-config ise” to reset ISE application.

Unfortunately, the server could not start its service. So, I tried to use command “reset-config” to reset the server to factory default configuration.

After server finished reboot, Cisco ISE services was running normally but it has only “Application Server” service that cannot running.  It stuck in “initializing” state.

I already waited for 5 - 6 hours but it still stuck in “initializing” state. Moreover, I cannot enter GUI webpage to configure it.

I don’t know this is Cisco Bug or the server fail.

For more information, please find information below:

*****************************************
Displaying ISE application status ....
*****************************************
ISE PROCESS NAME STATE PROCESS ID
--------------------------------------------------------------------
Database Listener running 4601
Database Server running 40 PROCESSES

Application Server initializing

Profiler Database running 5730
AD Connector running 7513
M&T Session Database running 3439
M&T Log Collector running 7366
M&T Log Processor running 7261
Certificate Authority Service running 7217
SXP Engine Service disabled
pxGrid Infrastructure Service disabled
pxGrid Publisher Subscriber Service disabled
pxGrid Connection Manager disabled
pxGrid Controller disabled
Identity Mapping Service disabled

Please suggest how to resolve this problem.

[orp]

I'm not sure whether I'm answering exactly your question but I'll tell you this: ISE has some minimum requirements that are absolutely required. While it may seem to work even with lesser resources it actually doesn't and the error messages are rather cryptic if at all exist. Some services might simply not start up for no apparent reason. I noticed that when I had less than 200 GB free space and even though not all disk space was actually taken, ISE still didn't work correctly.

For the NICs I'd suggest that you change their type to one of the supported types and check the system's state at that point. Don't waste your time trying to understand why the system doesn't work.

[laurathaqi]

Hi all, 

I am facing similar issue with my Primary ISE NODE.

Case: ISE Distributed deployment was working fine for a couple of months. Due to some restructure of the network I needed to change the management IP.  In order to do that, based on Cisco documentation, I deregistered secondary node and make Primary node in standalone status. Changed the management IPs successfully, but when tried to register Secondary Node again, registration unsuccessful. Due to that, I restarted the Node, and now, the Application Server its stuck in the initializing state for more than 4 hours.

Action tried so far: 

- Application stop ise

- Application start ise

- VM restart 2 x times

- Node deregister and try to register again.  

Any thoughts would be highly appreciated.   

Thank you,

Laura 

[Marcelo Morais]

Hi @laurathaqui,

 try the following on the "Secondary Node" (now a Standalone Node

1. Export the Certificate

Administration > System > Certificates > Certificate Management > System Certificates

2. at the CLI

ise/admin# application reset-config ise

3. reload the "Secondary Node"

4. try to register the "Secondary Node" to your ISE Cube.

Hope this helps !!!

[laurathaqi]

Hi @Marcelo Morais 

Thank you for your reply!

After the restarts, I waited overnight and the appliance came back. This is the second time it is happening, and that I am needing to wait for more than 12 hours in order for the server to some into running  state. Weird behavior, but planning to investigate it with TAC. Will keep you updated. 

Thank you,

Laura 

[laurathaqi]

Hi, 

Just as I noted before, 24 hours rest and all went into its running state. Could not find reason why, but this happened to me two times now. Not sure how to approach it. 

Hope it helps someone! 

Thank you,

Laura 

[Marcelo Morais]

Hi @laurathaqi ,

 are you able to follow the procedure that I described on Apr, 28th?

[laurathaqi]

Hi @Marcelo Morais 

I was not able to follow the procedure you suggested as per the limited time window I had to work in session with the client. I posted the question after that day client session ended, and the next day, the appliance was already running, so there was no need to apply the procedure suggested.

Your support is always much valued and appreciated. 

Thank you,

Laura