Cannot access CISCO ISE-3395-K9 Web GUI

[BINH_C_LE83]

Hi,

I'm having trouble accessing the ISE-3395-K9 web gui via interface gig 0 with ip address 192.168.1.10.  I set my labtop's ip address to 192.168.1.20 and could ping back and forth but am still not able to access via direct connection from my labtop to interface gig 0 using any of the supported web browsers.  Any help would be greatly appreciated.

[nspasov · Accepted solution]

It is possible that the GUI was configured to restrict access to only certain IPs / Subnets. If 192.168.1.x is not one of them then you won't get access. 

Are you able to login to the shell via SSH? If yes, you should check and confirm that all ISE related services are running by issuing the following command:

show application status ise

Thank you for rating helpful posts!

[BINH_C_LE83]

This was brand new ISE that I configured, so it didn't any prior configs.  I typed "show application status ise" after the "application start ise" command and it still showed that none of the applications are running.  Maybe this is why I'm not able to access the web gui?

setup/admin# show application status ise

ISE Database listener is not running
ISE Application Server process is not running.
ISE M&T Session Database is not running.
ISE M&T Log Collector is not running.
ISE M&T Log Processor is not running.
ISE M&T Alert Process is not running.

setup/admin#

[nspasov · Accepted solution]

OK, so that is the problem. You can try one of the two things while in the shell:

1. Reload the server with the "reload" command

2. Try starting the services manually with the "application start ise" command. Then wait 10-15 min and issue "show application status ise" again to confirm that all services are running. 

Thank you for rating helpful posts!

[BINH_C_LE83]

I got it working.  I entered "application reset-config ise" to reset to factory-default.  After reloading, the ISE services started running and I was able to access the WEB gui.  Thanks for everything.

[nspasov]

Glad you got back into it and sorry that you had to reset the config :(

Now, if your issue is resolved, you should mark the thread as "answered" :)

Thank you for rating helpful posts!