ISE Repository wrong reading

[jpirc]

Hello,

On Cisco ISE, I created an SFTP repository. When I try to read the contents of the repository, I get duplicate names. Because of this, I cannot download a patch or perform a restore. When I check on the SFTP server, files have correct names.

[Aref Alsouqi]

Where do you see the duplicate names? I can't see any duplicate.

[jpirc]

Hello, it should be:

Weekly_Configuration-Data-CFG10-240830-0000.tar.gpg

But it is:

Weekly_Configuration-Data-CFG10-240830-0000.tar.gpgWeekly_Configuration-Data-CFG10-240830-0000.tar.gpg

On SFTP server the names are correct:

[Aref Alsouqi]

Oh I see, thanks for clarifying that. Not sure, I would try to remove the repository from ISE and recreate it and see if that helps.

[jpirc]

Thaks for quick response Aref, but still not working.

I have tried:

Create SFTP on Win10 and Win Server2022. SFTP server is Solarwinds. When connecting with WinSCP to this two servers I can see correct names. But ISE reading is wrong. 

Then I create once again SFTP Repository on two new ISE VM version 3.3. Patch4. And it was the same thing.

[Aref Alsouqi]

That is really interesting. I would think this could be a bug that is causing this, and I would suggest reach out to TAC.

[andy-breaux]

So, I created a ticket with Cisco TAC a couple of weeks ago in reference to this same issue and my case is still open. Hopefully, this will help some of you. Cisco is still looking into this, but here is I have found to be the issue:

***ISE repository Work Fine - No Issues – Using SolarWinds SFTP Server Version 1.0.4.9 ******

There were no issues when using SolarWinds version 1.0.4.9. Everything worked as expected (Backup and Restoration of Cisco ISE).

***ISE repository Not working -- ISE repository shows file name with duplicates -Using SolarWinds Version 2.2.4.60039 & 2.2.7.60059 *****

I would recommend for anyone using the latest release of SolarWinds SFTP server software for your Cisco ISE backups, to validate and made sure you do not see duplicate file names otherwise the restore process will fail.

[andy-breaux]

I should probably add that I have tried this in my home lab using Cisco ISE 2.7, 3.1, and 3.3 with no change in behavior.

[andy-breaux · Accepted solution]

Cisco created a bug about this issue. The backup file is still usable via CLI restoration. Here is the link to the bug CSCwo70665 : Bug Search Tool

[Aref Alsouqi]

Thanks for sharing this.