We are standing up a new ISE 2.2 Deployment alongside our current production 2.0.1 deployment. Aim is to test the 2.2 Deployment and then move production over to it.
We have spun up a new 2.2 Standalone VM. Plan is to restore Configuration & Operational Backups from 2.0.1 Deployment to new 2.2 Admin Node. Then add additional v2.2 PSN's & backup Admin/Monitoring Node.
Question - Once the configuration backup is restored in 2.2 will the old deployment nodes show up in the Deployment? If so is there any risk that this could affect out 2.0.1 Production deployment?
If the primary ISE node of the new ISE 2.2 deployment has a different hostname than that the CFG backup is taken from, the restore will drop the deployment. If you are still concerned, then put some black-hole routes between the two deployments.
If the primary ISE node of the new ISE 2.2 deployment has a different hostname than that the CFG backup is taken from, the restore will drop the deployment. If you are still concerned, then put some black-hole routes between the two deployments.
Thanks for the answer. The new ISE 2.2 deployment has different IP's and hostnames. Can you null route current production nodes directly on the the 2.2 server?
This is how I do most of my upgrades and have never had any disruption occur against the old deployment.
If you don't want to build all new VMs/hostnames/IPs you can use your 2.2 VM as the temporary anchor point for 2.2. Test against it then start migrating over the 2.0.1 nodes one at a time by rebuilding them to 2.2 and adding them to the 2.2 deployment. Once you finish you can move personas around to the way they were in 2.0.1 and detroy the temp VM you started out with. Or turn that into your lab ISE VM.
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
