02-03-2021 08:53 AM
Hi,
Is it applicable to migrate Virtual Cisco ISE to Cisco ISE 3615?
Is it Applicable to get Back-up from the Current existing Virtual Cisco ISE and restore it on Cisco ISE 3615?
Thanks in Advance,
Solved! Go to Solution.
02-03-2021 08:59 AM
Make sure you have same resource and version of ISE installed on Appliance
Backup your Operations, Configuration information and data from VM.
Restore in Appliance.
Regarding License Move contact cisco License team ( they may help you).
02-03-2021 09:13 AM
Are you looking to upgrade the version of ISE you are running, if so then that can add some complexity? Or are you looking to just straight add/replace nodes?
Assuming you are running version 2.4 of newer, then the easiest way to do this is to shut down the node you are replacing, start up the new appliance or VM, run through the set up, then add the new node to the deployment by registering it. This way you can reuse IP's, hostnames, DNS entries and don't have to go through a backup/restore. It is a low impact easy way to replace nodes.
It's also supported to run virtual and physical appliances in the same deployment, and it's also supported to run different size nodes in the same deployment. The important part is to understand and know the scaling limitations of each though.
02-03-2021 08:59 AM
Make sure you have same resource and version of ISE installed on Appliance
Backup your Operations, Configuration information and data from VM.
Restore in Appliance.
Regarding License Move contact cisco License team ( they may help you).
02-03-2021 09:13 AM
Are you looking to upgrade the version of ISE you are running, if so then that can add some complexity? Or are you looking to just straight add/replace nodes?
Assuming you are running version 2.4 of newer, then the easiest way to do this is to shut down the node you are replacing, start up the new appliance or VM, run through the set up, then add the new node to the deployment by registering it. This way you can reuse IP's, hostnames, DNS entries and don't have to go through a backup/restore. It is a low impact easy way to replace nodes.
It's also supported to run virtual and physical appliances in the same deployment, and it's also supported to run different size nodes in the same deployment. The important part is to understand and know the scaling limitations of each though.
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