ISE upgrade 2.0 to 2.2 order and problem with GUI

[RYAN PAUL]

Hi everyone,

I'm relatively new to ISE, so please forgive my ignorance. 

I currently have a small ISE deployment with one 3315 acting as the PAN and MNT.  I also have 1 VM in the PSN mode. 

In a deployment scenario like this, what is the correct upgrade order?  PSN then PAN/MNT?

Also, the fist time I looked at the upgrade process through the GUI, I entered the Repository and Bundle name.  The bundle name had a (1) in the file name.  When I try to go back in to change the name because the (1) is invalid, there is no option to change the bundle name...only the repository.  How can I change that?

Thanks,

Ryan

[Rahul Govindan]

You need to have a secondary Admin node to start the upgrade. You can make your PSN as secondary Admin node and upgrade that first. Once that is done, you can have your old Primary Admin + MnT node upgraded.

http://www.cisco.com/c/en/us/td/docs/security/ise/2-2/upgrade_guide/b_ise_upgrade_guide_22/b_ise_upgrade_guide_22_chapter_010.html

Ideally you would want to have redundant nodes for all personas to have zero downtime upgrade, but the above method should work.