02-09-2022 05:10 PM
Just a question regarding the ISE GUI upgrade sequence.
GUI allows choosing the sequence of the nodes, I am wondering if I have two node deployment (i.e. primary and secondary), the secondary admin node (backup node) needs to be upgraded first and then primary admin node, but what if I don't choose the primary admin node.
Would the upgrade process stop once the secondary admin node is upgraded? What would HA look like in this scenario, i.e. version mismatch?
Would it be possible to use GUI again to upgrade the primary node at a later time?
Solved! Go to Solution.
03-05-2022 04:09 PM
Learn the options to migrate your ISE deployment to the latest version. This will prepare you with strategies to upgrade your deployment to take advantage of the latest features.
You will learn :
00:20 Agenda
01:44 ISE Versions and Suggested Releases
02:57 ISE 3.1 Release Features
03:40 Supported Releases for Upgrading to ISE 3.1
06:02 Upgrade Workflow
07:04 Upgrade Methods: Backup & Restore, GUI, or CLI
11:00 Upgrade Preparations: Backup, Certs, Health Check
14:32 Upgrade Options Overview: Split and Full Upgrades
17:40 Full Upgrade Process Details
21:28 Upgrade Pre-Checks
27:09 Demo of Full Upgrade from ISE 2.7 to 3.1
38:45 Split Upgrade Process Details
44:11 Demo of Split Upgrade from ISE 2.6 to 3.1
52:38 Split vs Full Upgrade Process Comparison
54:38 Post Upgrade Tasks
56:13 ISE Upgrade Resources
02-09-2022 07:57 PM
Hi, what is the ISE version. check below link for version 2.7. you better understand upgrade process clearly before start.
02-10-2022 04:32 AM
Definitely take a peek at the shared guide from @Kasun Bandara
Would the upgrade process stop once the secondary admin node is upgraded? What would HA look like in this scenario, i.e. version mismatch?
-In this scenario you would be in a split deployment. Not sure why you would consider doing one node and not the other.
Would it be possible to use GUI again to upgrade the primary node at a later time?
-What is the version path (to/from)? Take a look at this discussion for additional information too: Upgrade ISE from 2.7 to 3.1 - Cisco Community
-Lastly, if going to 3.0 there are licensing model changes that you should be aware of: Products - ISE Licensing Migration Guide - Cisco
03-05-2022 04:09 PM
Learn the options to migrate your ISE deployment to the latest version. This will prepare you with strategies to upgrade your deployment to take advantage of the latest features.
You will learn :
00:20 Agenda
01:44 ISE Versions and Suggested Releases
02:57 ISE 3.1 Release Features
03:40 Supported Releases for Upgrading to ISE 3.1
06:02 Upgrade Workflow
07:04 Upgrade Methods: Backup & Restore, GUI, or CLI
11:00 Upgrade Preparations: Backup, Certs, Health Check
14:32 Upgrade Options Overview: Split and Full Upgrades
17:40 Full Upgrade Process Details
21:28 Upgrade Pre-Checks
27:09 Demo of Full Upgrade from ISE 2.7 to 3.1
38:45 Split Upgrade Process Details
44:11 Demo of Split Upgrade from ISE 2.6 to 3.1
52:38 Split vs Full Upgrade Process Comparison
54:38 Post Upgrade Tasks
56:13 ISE Upgrade Resources
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