To fix the issue with the PSN got stuck at step 4 there were no many options apart from rebuilding the PSN or to reset its ISE application configuration.
#CISCO ISE 2.4 DEPLOYMENT UPGRADE#
However, the second issue was with the secondary PAN which for some reason was keeping one of the PSNs in its deployment even though that PSN was already upgraded and added to the new upgraded deployment.īecause of that I was not able to upgrade the secondary PAN since one of the requirements is to complete the upgrade of all the other nodes before starting or being able to upgrade the secondary PAN itself.Īlong with Cisco TAC we spent some time doing some troubleshooting to try to find out the root cause of these issues with no luck. That was the case until one PSN got stuck at step 4 which took really too long before it failed the upgrade process. When I started the upgrade everything was progressing as normal and so far there were no major issues. It is also much more reliable in my opinion because it prevents running into potential browsers dependent issues such as sessions timing out or unrealistic percentage bars when provisioning the ISE upgrade image.Īs expected, the plan to do the upgrade was to start with the secondary PAN and then moving to the PSNs, and finally upgrading the new secondary PAN which was the old primary PAN. I was doing the upgrade through CLI which is my favorite option over the GUI because it really gives much more control and visibility. This project was to upgrade a distributed ISE cube with six nodes from version 2.2 to 2.4 and all appliances were virtual.
![cisco ise 2.4 deployment cisco ise 2.4 deployment](https://i2.wp.com/www.allthingsnetworking.net/wp-content/uploads/2021/02/Upgrade-New-Deployment-ISE.png)
These issues were, an ISE PSN got stuck at step 4 during the upgrade process, and a PAN went out of synch. I came across a couple of issues during an ISE upgrade project I was working on recently which are not really common and you would rarely see them.