Cisco Cisco Identity Services Engine 2.1 Manual Técnica
Check if ISE is properly acting as a DNS sinkhole. A packet capture can help confirm if the request
is going to ISE and if the ISE responds to it with its own IP address:
is going to ISE and if the ISE responds to it with its own IP address:
Check if the HTTP redirect works properly. After it gets the resource IP address and establishes a
TCP connection to ISE, the client sends an HTTP GET request to the ISE. This can be confirmed
in a client side packet capture:
TCP connection to ISE, the client sends an HTTP GET request to the ISE. This can be confirmed
in a client side packet capture:
At the same time, ISE determines if any session exists for this client. This process of session
lookup on ISE can be checked in prrt-management log:
lookup on ISE can be checked in prrt-management log:
After the session lookup, ISE returns the redirect URL to the client in an HTTP 302 response: