This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.
We have a 7 node deployment (3PSN, 2PAN, 2MNT) currently on 2.2p10. We ran the URT and everything came out fine.
However, upon upgrading the secondary PAN first, we encountered an issue that after the VM rebooted it ended up in the grub rescue prompt. TAC said we have to rebuild this node, instead we restored the LUN from before the upgrade. We believe this issue is due to all the relics in the system from all the bugs/patches we hit/applied in 2.2. In the end of the day, upgrading from 2.2 to 2.4 is too disruptive and requires WAY to much knowledge of 'under the hood' of ISE to make it happen (it's not easy). Plus we want to start with a clean DB.
Is there a document on how to build a parallel ISE deployment using config backups in a manner that it will not trample on our production deployment?
Solved! Go to Solution.