cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
52679
Views
105
Helpful
20
Replies

ISE Indexing Engine is not running.

jose.garcia1
Level 1
Level 1

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.

Screen Shot 2017-11-02 at 9.53.04 AM.png

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.

4 Accepted Solutions

Accepted Solutions

Timothy Abbott
Cisco Employee
Cisco Employee

Jose,

You will need to open a TAC case to further investigate why that process is not starting.

Regards,

-Tim

View solution in original post

Check your reverse dns records for ise nodes. Without them ISE Indexing Engine don''t run in cluster.

View solution in original post

jason.emery
Level 1
Level 1

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

View solution in original post

Please open a tac case and update thread

View solution in original post

20 Replies 20

Timothy Abbott
Cisco Employee
Cisco Employee

Jose,

You will need to open a TAC case to further investigate why that process is not starting.

Regards,

-Tim

Hi,
What is the impact when ISE indexing service is not running? Does it impact to device admin feature?

hslai
Cisco Employee
Cisco Employee

This provides data for ISE dashboard and ISE context visibility. It has no impact on Device Admin (TACACS+) services.

omer shtivi
Level 1
Level 1

Hi,

Did you find the problem? has the same issue here

BR

Omer Shtivi

Check your reverse dns records for ise nodes. Without them ISE Indexing Engine don''t run in cluster.

It worked!

Thank you very much!

omer shtivi
Level 1
Level 1

Solved the problem.

Thanks!

hi

how did you solve it ?

i am getting same service error on v2.3

omer shtivi
Level 1
Level 1

Reverse A record.

You need that when you do a ping -a <ISE IP> you get the DNS name.

bingo...!

it is worked .

thanks a lot omer

Muhammad Azhar
Level 1
Level 1

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.

i have cheked all reqs. fresh install. but Index does not starts
ise/admin# ping ise
PING ise (10.0.64.228) 56(84) bytes of data.
64 bytes from 10.0.64.228: icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from 10.0.64.228: icmp_seq=2 ttl=64 time=0.028 ms
64 bytes from 10.0.64.228: icmp_seq=3 ttl=64 time=0.020 ms
64 bytes from 10.0.64.228: icmp_seq=4 ttl=64 time=0.039 ms

--- ise ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 0.020/0.028/0.039/0.009 ms

ise/admin# sh clock
Mon Jun 17 14:39:34 MSK 2019
ise/admin#

jason.emery
Level 1
Level 1

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

All nodes in a cluster need to be in the same timezone by design? Where is that written?
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: