cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
14443
Views
6
Helpful
7
Replies

Context Visibility not working

toth.mate.istvan1
Frequent Visitor
Frequent Visitor

Hello,

 

I was wondering if any of you guys encountered the issue that when you click on the Context Visibility page, I get the attached error (I am after a hostname change, but stayed in the same domain).

 

"Unable to load Context Visibility page. Ensure that reverse DNS lookup is configured for all Cisco ISE nodes in your distributed deployment in the DNS server(s). Exception: all shards failed"

 

I re-generated the ISE CA Chain and DNS records are also OK. I tried a lot of other settings too, but none of them solved the problem. 

 

Do you have any suggestion about where else should I investigate? (I am using ISE 2.6, standalone deployment)

 

 

Thank you,

Matt

1 Accepted Solution

Accepted Solutions

Ensure Reverse DNS is configured for ISE - You need to be able to resolve IPs to DNS name.
So make sure you add the DNS PTR records.

 

Refer : Community Thread

Regards,
Sathiyanarayanan Ravindran

Please rate the post and accept as solution, if my response satisfied your question:)

View solution in original post

7 Replies 7

Ensure Reverse DNS is configured for ISE - You need to be able to resolve IPs to DNS name.
So make sure you add the DNS PTR records.

 

Refer : Community Thread

Regards,
Sathiyanarayanan Ravindran

Please rate the post and accept as solution, if my response satisfied your question:)

Hi @Sathiyanarayanan Ravindran ,

Where the DNS PTR records should be added ?  i am having the same issue.

''Unable to load Context Visibility page. Ensure that reverse DNS lookup is configured for all Cisco ISE nodes in your distributed deployment in the DNS server(s). Exception: all shards failed''

Thanks,
Sudarshan

This procedure worked for me. Thank you, Emre. 

wsalam
Community Member

have you faced any down time during this procedure, or any end point data was lost?

 

No, I didn't experience any downtime during this procedure. I couldn't remember any data loss.