09-14-2017 11:00 AM
Hi,
a quick question, if we are going to upgrade 8 nodes deployment environment, shall we upgrade all nodes from 2.1 to 2.2 then patch them togehter ? or shall we upgrade each node to 2.2 and fully patch it ?
Solved! Go to Solution.
09-15-2017 01:24 PM
Best to note before upgrade
Use the new upgrade readiness tool
Validate your use cases in a lab or limited production before with new version of code
Also you can do a split deployment upgrade where someone network devices will point to old deployment and some a new deployment
09-14-2017 12:42 PM
To follow the upgrade via the web UI, all nodes to be upgraded first before patching. If not using the web UI, then you may do either. I would suggest to upgrade 2 ~ 4 nodes first and fully patch and test.
09-14-2017 06:32 PM
Having done many upgrades I wouldn't recommend using the Web upgrade or the CLI upgrade path. If things go wrong you are going to spend a lot of time trying to recover. The fresh install/restore method if very predictable and controllable.
Take a backup.
Promote backup admin node to primary
Take the backup admin node (used to be primary), rebuild it from ISE 2.2 .iso or deploy 2.2 OVA. Rebuild this one first as all the license files are usually tied to this serial #.
Restore the backup
Reinstall/Rehost licenses
Apply patch
Join to AD, check certs
Enable Deployment
At this point you have your 2.2 anchor point up and running then you can control the upgrade by reimaging each 2.1 box one at a time and bring them into 2.2. I have done large deployments using this method during the day with no disruption to service. You have total control of the process and easy backout. Last box to convert is the admin node in 2.1 deployment.
09-15-2017 12:51 PM
thank you, guys. we got upgraded to 2.2. it took us long time to finish.
after the upgrade, we start hitting bug CSCvf57412 and no solution ....
ISE reallly has too many bugs ...
09-15-2017 01:24 PM
Best to note before upgrade
Use the new upgrade readiness tool
Validate your use cases in a lab or limited production before with new version of code
Also you can do a split deployment upgrade where someone network devices will point to old deployment and some a new deployment
09-15-2017 02:17 PM
HI Jason,
our use cases tested and works, only thing really annoying the 2.2 web GUI, keep telling me : " Oops"
09-15-2017 02:45 PM
Ok make sure you contact tac for attachment to the defect so they can get a patch out
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