cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
987
Views
1
Helpful
2
Replies

ISE Backup and Restore Question

pmcternan
Level 1
Level 1

Hello Community,

I am in the process of upgrading our ISE hardware from SNS-3595-K9 Version 2.7 to SNS-3755-K9 Version 3.1 and I am at the point where I will be restoring the data to our new environment from the shared repository we have set up that runs our backups for our current environment. A little information. This is a 6 node distributed deployment 2 PAN, 2 PSN and 2 MnT. The FQDN and IP's are changing. Do I need to check off the Restore ADE-OS checkbox? I would also like to confirm that I can restore configs from 2.7 to 3.1. Thanks in advance. 

1 Accepted Solution

Accepted Solutions

Restoring ISE 2.7 backup onto 3.1 should work with no problems. If you keep "ade-os" option off the restore won't include the hostnames nor the IP addresses details. One thing to remember is that ISE 2.7 licenses need to be converted to ISE 3.x model prior to the upgrade.

To do that you should engage with Cisco licensing team providing them with the SO# of your 2.7 deployment, company name, and how many nodes you have, when you are planning to migrate to ISE 3.1, and then they will  convert the licenses from 2.7 > 3.x decommissioning the old licenses. However, they would also create a new temporary licenses set for your ISE 2.7 deployment to allow you to revert back to the old environment in case it is needed, they might ask you how many licenses should be generated for the temporary set. You should find all the temporary and the newly converted licenses in your smart account after the licensing team finished working on your case. You should also migrate TACACS licenses if you don't have them already in your smart account.

Once you are happy with the newly created deployment you can inform the licensing team that you don't need the temporary licenses any more and they will remove them from your smart account.

Also, please remember that if you will keep the new IP addresses on the new PSNs, you should change the RADIUS/TACACS servers details on all network devices to reflect the new IP addresses.

View solution in original post

2 Replies 2

Restoring ISE 2.7 backup onto 3.1 should work with no problems. If you keep "ade-os" option off the restore won't include the hostnames nor the IP addresses details. One thing to remember is that ISE 2.7 licenses need to be converted to ISE 3.x model prior to the upgrade.

To do that you should engage with Cisco licensing team providing them with the SO# of your 2.7 deployment, company name, and how many nodes you have, when you are planning to migrate to ISE 3.1, and then they will  convert the licenses from 2.7 > 3.x decommissioning the old licenses. However, they would also create a new temporary licenses set for your ISE 2.7 deployment to allow you to revert back to the old environment in case it is needed, they might ask you how many licenses should be generated for the temporary set. You should find all the temporary and the newly converted licenses in your smart account after the licensing team finished working on your case. You should also migrate TACACS licenses if you don't have them already in your smart account.

Once you are happy with the newly created deployment you can inform the licensing team that you don't need the temporary licenses any more and they will remove them from your smart account.

Also, please remember that if you will keep the new IP addresses on the new PSNs, you should change the RADIUS/TACACS servers details on all network devices to reflect the new IP addresses.

pmcternan
Level 1
Level 1

Great information. Thank You Aref. Since the FQDN's and IP's are going to be different I will try it without checking the ADE-OS first and let you know here how it worked.