Solved: Re: ISE appliance: stuck Upgrading Nodes

jaheshkhan · ‎10-30-2023

To I upgraded Two node ISE from 3.0 to 3.2. but after upgrading my primary node become secondary and it shows upgraded

but when i went to upgrade page it shows overall upgrade process. stuck the status even after two hours.

May I know what to do in this situation. I went with split upgrade option and that was the only option available for me.

marce1000 · ‎10-30-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! '

View solution in original post

Greg Gibbs · ‎10-30-2023

If this is a Production issue, you would be best opening a TAC case to investigate immediately.

If this is not a Production issue, your best bet would likely be to re-image the old P-PAN with ISE 3.2, de-register the old node from the Deployment on the new acting P-PAN, register the node back as the Secondary PAN, then promote it back to Primary PAN after the sync.

View solution in original post

marce1000 · ‎10-30-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! '

Greg Gibbs · ‎10-30-2023

If this is a Production issue, you would be best opening a TAC case to investigate immediately.

If this is not a Production issue, your best bet would likely be to re-image the old P-PAN with ISE 3.2, de-register the old node from the Deployment on the new acting P-PAN, register the node back as the Secondary PAN, then promote it back to Primary PAN after the sync.