ISE Upgrade from 2.4 to 2.6 Question

[baker82]

due to a recent security vulnerability found, we are pushing our ISE deployment v2.4 to v2.6 patch 2

I was hoping to get some input on others experiences on this upgrade process. Im hoping there are some others out there with similar deployment types. We have a 7 node distributive deployment which are comprised of mostly conus nodes, however, we do have one node which is oconus and the network bandwidth between our PAN and SAN to the other nodes can be pretty slow at times.

I want to know if this is going to pose any problems proceeding forward with GUI upgrade to v2.6 or should I look at updating via CLI. 

maybe there is a way to push these upgrade bundle to the individual nodes prior to upgrade and then when the update begins, the administrative node can just use the local copy of the file instead of trying to push it over a WAN link. (I assume it works like this) 

[jj27 · Accepted solution]

You should be able to transport the 2.6 upgrade GZIP (ise-upgradebundle-2.1.x-2.4.x-to-2.6.0.156.SPA.x86_64.tar.gz) file directly to the local node storage from the CLI, then follow the upgrade guide to upgrade the nodes one at a time via the CLI with the application upgrade prepare and application upgrade proceed commands.

Remember to follow the upgrade guide and run the URT before upgrading.

[baker82]

thank you for the reply.

2.4 patch 10 resolved the vulnerability we found so there was no need to update to 2.6 however, i have marked as a solution. thank you again for the support!