cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1006
Views
3
Helpful
5
Replies

Brand new virtual ISE cannot access the gui

sandfed@cisco.com
Cisco Employee
Cisco Employee

Just installed the small version of the virtual ISE. Other than the oddity with the port not being assigned as expected install and activation is fine. SSH and ping from my machine to the ISE works fine. Yet https to the ip results in "unable to connect" from both firefox and safari. Did the application stop and start with no change to the situation. Tried both https://{ip} and https://{ip}/admin same result. What simple step have I likely missed?

 

Version information of installed applications
---------------------------------------------

Cisco Identity Services Engine
---------------------------------------------
Version : 3.2.0.542
Build Date : Wed Oct 19 16:27:24 2022
Install Date : Fri Dec 22 07:45:45 2023


testise/admin#

 

 

5 Replies 5

balaji.bandi
Hall of Fame
Hall of Fame

When you install ISE, ISE take Long time to build. - check all services are running ?

#show application status ise

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

The application says its running...

 

 

 

check command level :

#show ports | in 443

Try telnet to ISE ip with port 443

Try restarting the application ( after restart check again services all running and try access?)

#application stop ise
#application start ise

 

Note : i am in impression, ISE and Device you connecting same LAN, if they are different check any Firewall between which blocks your 443 access.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Marvin Rhoads
Hall of Fame
Hall of Fame

Did you by chance disable ipv6 on your Gi0 interface? It must be enabled as some internal docker containers use IPv6. When it is disabled, the application server will be running but the ISE server will fail to listen on tcp/443 for the Apache web server GUI.

There's a BugID on this but I can't locate it at the moment.

FYI the bug I mentioned can be found here: https://bst.cisco.com/bugsearch/bug/CSCwa08018