Solved: Issue with an ISE upgrade to 3.2

KevinTicehurst35045 · ‎09-05-2023

Hi all, Upgrading Cisco ISE through GUI from 3.1 to 3.2 (bundled with patch 3). The primary admin node has successfully upgraded (despite the docs saying the secondary should upgrade first). However all the other nodes have been stuck in Upgrade Queued for over 2 hours with no activity. Any ideas on how to proceed ?

Ben Walters · ‎09-06-2023

You can check the progress of the upgrade for each node using the CLI, the below command should show you if the upgrade process has started or not.

show logging system ade/ADE.log | in STEP

If you check with the CLI and it looks like the upgrade hasn't started on the nodes and nothing is happening you could then try upgrading through the CLI which I found to work a little better than the GUI most of the time. You just need to make sure the upgrade package is accessible from each node either locally or on a remote repository.

View solution in original post

marce1000 · ‎09-05-2023

- FYI : https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/220195-troubleshoot-identity-services-engine-i.html

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Ben Walters · ‎09-06-2023

You can check the progress of the upgrade for each node using the CLI, the below command should show you if the upgrade process has started or not.

show logging system ade/ADE.log | in STEP

If you check with the CLI and it looks like the upgrade hasn't started on the nodes and nothing is happening you could then try upgrading through the CLI which I found to work a little better than the GUI most of the time. You just need to make sure the upgrade package is accessible from each node either locally or on a remote repository.

KevinTicehurst35045 · ‎09-06-2023

Thanks Ben, Yes was running that log and basically nothing happened apart from the primary admin node upgrading. Total pain as it left the other nodes in limbo so ended up having to make them stand alone, upgrading through CLI and then rejoining. All took way longer than it should have done. The old split upgrader still seems to work as with that one you can select the order of things. The new full upgrade process in the GUI I wont be using again

KillBill66 · ‎01-23-2024

I'm curious, if you upgrade the Primary Admin of old deployment, it will become Primary of the new deployment. What happens to the Secondary of the old deployment? does it become Primary of the old dep. ? does it have to manually be promoted? Because it seems to me that if you started upgrade process from Primary of old dep. and it leaves and forms a new dep. then there was nothing left in the old dep. to run the upgrade flow to all the remaining nodes.