topic Re: Cisco ISE Not access via HTTPS in Network Access Control

Cisco ISE Not access via HTTPS

kiransc586282 — Wed, 19 May 2021 22:06:35 GMT

I have installed the Cisco ISE on VMware Esxi. But ISE can access via SSH and not access via http or https. Kindly suggest the procedure of ISE access via http or https.

Re: Cisco ISE Not access via HTTPS

Rob Ingram — Wed, 19 May 2021 22:12:03 GMT

@kiransc586282

What version of ISE are you using?

From the CLI run the command "show application status ise" and confirm the "Application Server" service is running. If it is running, try another browser.

Re: Cisco ISE Not access via HTTPS

kiransc586282 — Wed, 19 May 2021 22:16:36 GMT

Version 3.0

Application server is running fine and checked the different browser.

Re: Cisco ISE Not access via HTTPS

Greg Gibbs — Wed, 19 May 2021 23:37:51 GMT

The web server is started as part of the Application Server service, so there is nothing else that has to be done to start it.

You could use the 'show ports | include :443' command to verify that the node is listening on the port.

Example:

ise30-sa/admin# show ports | include :443
tcp: :::443

You could also use the 'tech dumptcp interface GigabitEthernet0' command to see if the node is seeing any tcp/443 traffic being received.

I would suspect that a firewall, ACL, or other access control is blocking the traffic between your admin PC and the ISE node.

Re: Cisco ISE Not access via HTTPS

kiransc586282 — Thu, 20 May 2021 11:24:59 GMT

ISE01/admin# sh ports | i 443
tcp: 127.0.0.1:8888, :::9080, 10.2.84.12:8443, 10.2.84.12:8444, 10.2.84.12:8445, :::9085, :::9090, :::9443, 127.0.0.1:2020, :::9060, :::9061, :::25318, :::9063, :::8905, :::5514, :::9002, :::1099, :::8910, :::9999
ISE01/admin#

But https port is not show in this command.

I can able to ping and ssh the device.

Re: Cisco ISE Not access via HTTPS

Greg Gibbs — Fri, 21 May 2021 05:27:35 GMT

This is not normal and appears that the installation may not have worked correctly. If you have not already rebooted the node, I would suggest doing so to see if it starts listening on tcp/443.

If you have already rebooted and see the same issue, I would suggest rebuilding the node and ensure you have followed all of the instructions (including VM specs and CPU/Memory reservations) as per the Install Guide.