Upgrade ISE Version 2.1 to 2.6 on existing SNS servers

[adleung]

Dear all,

My client is planning the procedure for migrating my four PSN (SNS-3515). They have four remote PSNs in two different countries away from the main ISE cluster in North America.  For those my client did not have to buy new because they are SNS-3515, but are currently in the ISE2.1 deployment and my client need to move those to the new deployment but need to be updated to 2.6 first.

Is it required to make those 4 x PSN standalone first?  During our discussion of migration option, we can think of three different options.  We don’t what will be the recommended next steps. 

1. From GUI remove PSN from existing 2.1 deployment,  from CLI run “ application reset-config ise”, from GUI upgrade it to 2.6 and then add it to the new 2.6 deployment (It looks like it is most easiest way)
   
2. From GUI remove PSN from existing 2.1 deployment and upgrade it to 2.6, from CLI run “ application reset-config ise”, and then from GUI add it to the new 2.6 deployment
3. From GUI remove PSN from existing 2.1 deployment, from CIMC re-image it to 2.6, put all configurations, then from GUI add it to the new deployment

Note: Option 1 and 2 are similar is just the step how the reset ISE configuration is different order.

Do you have any recommendations?

Regards,

Adrian

[hslai · Accepted solution]

Please read ISE Upgrade Best Practices first.

Actually we are updating that doc and a new revision will be up soon.

[adleung]

Dear all,

Do you have any comments on the options? My client is intended to migrate in the next month.

Regards,

Adrian

[hslai]

Please the doc I referred to in my previous response. (3) from your original question is what we usually recommending.