ISE Lab: Backup & Restore ISE

As this is a lab topology, it relies on lab licenses. For ISE this means that there is a 90 day period. The license I have has expired and requires fixing. This is quite simple to perform. All that needs to be done is a config backup taken from the old device and restored to a new device.

Create FTP Repo

The FTP repo can be created in the GUI or in the CLI. The CLI does warn you when creating that any repo created in the CLI cannot used be in the GUI.

Perform Backup

There are two types of backups, config and operational. The operational is not required for a lab. It is just the data that has already been collected. If this is an upgrade or a real backup, then the operational data should be taken.

Gather Running Config

The running config will be needed to paste into my new GNS3 appliance.

Setup New Device

This is my new device in GNS3. It is ready to have basic configuration applied before I can paste into the running config from the old appliance.

Restore Configuration

The backup is stored on the FTP server. Once the FTP repo has been created and checked, the GUI will be able to show the backed up files.
Select the file to restore, it will ask for the encryption key that was applied when the backup was taken. There is a tick box for restoring the ADE-OS which is the CLI part of ISE. I have chosen to restore this despite the fact I have already applied the config the old-fashioned copy/paste way.

The restore took about 20 minutes for me. But I have seen larger take a lot longer. Once the restore has completed, that’s it done. If the operational data is required, this can be restored now. I have not bothered as it is a lab.
To check the status of the restore, we can console or SSH into the device and run the command…

Rejoin AD

Now that the configuration has been restored. ISE will need to rejoin AD. For this, the credentials are required for the ISE account in AD. This is needed so ISE can successfully query AD. I have used an administrator account, which is not recommended, but easy for a lab environment.

For this in my lab I had the wrong hostname for the ISE instance. ISE cannot join AD with the incorrect hostname. I have corrected this, in the CLI. This required a restart of the services.

Leave a Comment

Your email address will not be published. Required fields are marked *