10-28-2015 08:47 PM - edited 03-10-2019 11:11 PM
Hi Folks
I have just upgraded our Cisco Identity Service Engines to version 2.0. The upgrade appeared to be error free and successful but I cannot get into the webpage of either ISE. I get the initial login screen but after that I get a blank page. I have checked all VM requirements and we are ok in that regard. Any one out there experienced anything like this?
10-29-2015 03:53 AM
Did you clear your browsers cache?
10-29-2015 05:12 PM
Hi Martin
Yes I have deleted the cache and it has made no difference.
01-20-2016 05:49 PM
I am aware of three types of admin accounts on Cisco ISE, one is local GUI, another is local CLI and AD accounts.
I had the same issue, it looks like not only the active directory integration is lost but also the LOCAL GUI ADMIN ACCOUNTS are gone from the config :
If someone can post a sanitized copy of the show run | b user I anticipate that we could recreate the GUI credentials from the command line if you still have access to it. the format of the command is slightly different.
This document below does not address this issue in particular:
http://www.cisco.com/c/en/us/td/docs/security/ise/2-0/release_notes/ise20_rn.html
Admin User Unable to Access the ISE Login Page Post Upgrade
01-20-2016 06:08 PM
Hi Muradhattar
We ended up blowing that VM away and reloading an earlier snapshot using 1.3.
01-21-2016 07:10 AM
That's another possible solution. Never thought of that.
01-28-2016 10:48 PM
application reset-passwd ise admin
this command resets the gui pw.
01-31-2016 08:43 AM
We had encountered the same issue few months back and discovered the VM was thin provisioned. As soon as we changed it back to thick provisioned, it worked fine. Cisco ISE supports both thick and thin provisioning. However, we recommend that you choose thick provisioning for better performance, especially for Monitoring nodes. If you choose thin provisioning, operations such as upgrade, backup and restore, and debug logging that require more disk space might be impacted during initial disk expansion.
HTH
~ Jatin
01-31-2016 03:30 PM
Thanks Jatin. If we decide to upgrade again I will check we are using fat provisioning.
01-31-2016 03:39 PM
Sounds Good !!
02-08-2016 01:59 PM
Do you have any information to support this? My understanding is since VMWare has increased it's block size and as disk speeds have increased, this is no longer an issue. we have our vm provisioned as thin with 600gb and our upgrades took 45m+ per node.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide