09-13-2023 12:56 PM
Good Afternoon!
We have two ISE servers, just upgraded from 2.4 to 3.0 about a month ago. Yesterday I went through the process of registering the ISE licensing with out smart account using the token. Inside Cisco license manager I can see it formed a connection with the ISE server. During the registration on the ISE server it timed out and now I can no longer login to the GUI, it just spins. I can login to the CLI and the ISE application is running. Individuals can also still connect on the wireless network that uses ISE for authentication, so it's still servicing clients. Anyone had this happen before, or any other thoughts :)?
Thanks for the help!
-Scott
09-14-2023 05:24 AM
Why stop at 3.0? 3.2 is now the suggested release and 3.0 has an EOL announced. https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/identity-service-engine-software-3-0.html
Did you install any patches on 3.0? What does "show application status ise" show on the CLI? Have the ISE VMs been excluded from any hypervisor snapshots or backup utilities?
09-14-2023 12:34 PM
Good Afternoon!
Appreciate your response. My plan is to upgrade to 3.2. I thought it might be good to get the smart licensing working on 3.0 before we did that. Here is a snip of "show application status ise"
We don't do any snapchats or backup utilities on the VM's. Just backups using the GUI inside ISE.
Appreciate the help!
-Scott
09-14-2023 01:44 PM
Did you install any patches on 3.0?
09-15-2023 06:02 AM
09-15-2023 06:19 AM
09-15-2023 07:06 AM
09-15-2023 07:11 AM
Patch from the CLI. That being said, the GUI not loading is concerning.
Yes, you should upgrade to 3.2.
09-15-2023 07:13 AM
09-15-2023 07:26 AM
Always patch to the latest patch release before upgrading.
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