cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
721
Views
2
Helpful
6
Replies

Upgrade from 2.1 to 2.2 with patch

csco11552159
Contributor
Contributor

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 ?

1 Accepted Solution

Accepted Solutions

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

View solution in original post

6 Replies 6

hslai
Cisco Employee
Cisco Employee

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.

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.

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 ...

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

HI Jason,

our use cases tested and works, only thing really annoying the 2.2 web GUI, keep telling me  : " Oops"

Ok make sure you contact tac for attachment to the defect so they can get a patch out

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: