ISE Config Restore hangs at Restore is in progress... - how to debug?

[Arne Bier]

Hello

Testing out a potential ISE 2.2 --> 2.6 migration.

I have an ISE 2.6 patch 3 lab system that I am trying to restore an ISE 2.2 config backup file (2.5GB size) onto.

My ISE 2.6 node was wiped using

application reset-config ise

I initiated the restore via the GUI - and after 1.5 hours all I see is this ... I thinks it's gone out to lunch ...

I checked that the pgp password is correct - and the pgp file is in tact, because I can extract contents using the Linux gpg command.

ise02/admin# show restore status
%% Configuration restore status
%% ----------------------------
%      backup name: Weekly_CFG10-200316-2130.tar.gpg\n
%       repository: ftp\n
%       start date:
%        scheduled: no
%   triggered from: Admin web UI
%             host:
%           status: Restore is in progress...
%       progress %:
% progress message:

%% Operation restore status
%% ------------------------
%  No data found. Try 'show restore history' or ISE operation audit report

Any ideas where I should start to check the logs?  This is a lab node, therefore no TAC support.

[Damien Miller]

If you haven't already, then I would try to restore it to a fresh 2.2 node. If that works, run the URT on it.

[Arne Bier]

Thanks @Damien Miller - I do suspect that my ISE 2.6 system is not as "clean" as I wished it was.

In the interim I will build a clean 2.6 system and try the restore again.

If that also fails, then I will eventually restore the file on a fresh 2.2 build - but I wanted to save myself the extra hassle. It's an early stage of investigation about how the config will look from 2.2 -> 2.6

I am currently unable to run the URT on the production system :-(

[Damien Miller]

I was only suggesting running the URT out of band if you were able to get it to restore to a lab 2.2 node.  I was thinking if there was some issue with the restore, then maybe it had to do with the data you were "upgrading".

Curious to see how you make out with this. Along the lines of your comment too, I've long wondered how well the "reset-config" works. I've had nodes fail resetting.  

[hslai]

Some reset-config related bugs:

CSCvh74979

CSCvj88674

CSCvd97861

CSCvf27927

CSCvf62556
CSCvh27177

[hslai · Accepted solution]

I would use ISE CLI to check logs.

show logging system ade/ADE.log tail
show logging app ise-psc.log tail

We would need TAC engaged, more than that.

[Arne Bier]

thanks guys - I left it running overnight and it completed.

I will use the commands in future

cheers