11-02-2017 07:54 AM
I get an error in the ISE console indicating the ISE Indexing Engine is not running.
When I run show application status ise in the cli I get the below screen shot.
I have tried to start and stop the ISE as well as rebooting the ISE appliance.
Can anyone provide info on how to resolve this issue.
Solved! Go to Solution.
11-02-2017 09:00 AM
Jose,
You will need to open a TAC case to further investigate why that process is not starting.
Regards,
-Tim
12-06-2017 01:25 AM
Check your reverse dns records for ise nodes. Without them ISE Indexing Engine don''t run in cluster.
04-09-2018 01:18 PM
The issues I have seen/heard on this are:
1. DNS - forward and reverse DNS must be working - also ISE nodes must have working DNS servers configured..
2. Admin Certificates - make sure all nodes have proper Admin certificate - they can be self-signed
3. Time/Timezone - from CLI - make sure the NTP is working properly and all nodes have the same timezone configured.
Jason
06-18-2019 04:26 AM
11-02-2017 09:00 AM
Jose,
You will need to open a TAC case to further investigate why that process is not starting.
Regards,
-Tim
11-01-2018 07:33 AM
11-01-2018 01:26 PM
This provides data for ISE dashboard and ISE context visibility. It has no impact on Device Admin (TACACS+) services.
12-04-2017 11:23 AM
Hi,
Did you find the problem? has the same issue here
BR
Omer Shtivi
12-06-2017 01:25 AM
Check your reverse dns records for ise nodes. Without them ISE Indexing Engine don''t run in cluster.
01-24-2020 05:11 AM
It worked!
Thank you very much!
12-06-2017 10:36 PM
Solved the problem.
Thanks!
12-07-2017 11:04 AM
hi
how did you solve it ?
i am getting same service error on v2.3
12-07-2017 11:09 AM
Reverse A record.
You need that when you do a ping -a <ISE IP> you get the DNS name.
12-07-2017 11:26 AM
bingo...!
it is worked .
thanks a lot omer
01-25-2018 04:49 AM
I found the same problem after I upgrading from 2.0.0 to 2.3 ( ISE index engine not running ).
By adding revers DNS record it solve the issue. Some time you need to restart the ISE node.
06-17-2019 04:40 AM
04-09-2018 01:18 PM
The issues I have seen/heard on this are:
1. DNS - forward and reverse DNS must be working - also ISE nodes must have working DNS servers configured..
2. Admin Certificates - make sure all nodes have proper Admin certificate - they can be self-signed
3. Time/Timezone - from CLI - make sure the NTP is working properly and all nodes have the same timezone configured.
Jason
11-02-2018 06:45 AM
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