ISE Upgrade Verify File once copied into Local Repositry

[stuart.pannell]

Hi All, I am in the process of upgrading a standalone ISE deployment and have uploaded the upgrade package to a repository on the ISE server. Unfortunately the file was over 10GB and took an age to upload and as such I left it running over night. Now I want to verify the file yet cannot see a way of doing this?

ISE version is 2.7.0 Patch 10, upgrading to 3.0.X 

Is there a way to verify the file or would the verification that ISE does when preparing the package be available in a log file anywhere?

[k2no]

Hi,

You can take a look at the md5 checksum:

md5sum filename

 and then compare it to the one provided by Cisco to check the integrity of your file.

[Marcelo Morais · Accepted solution]

Hi @stuart.pannell ,

 remember that the command has a Verifying step:

ise/admin# application install ise-urtbundle-<version>.SPA.x86_64.tar.gz <repository>
 Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
 Generating configuration...
 Saved the ADE-OS running configuration to startup successfully

 Getting bundle to local machine...
 Unbundling Application Package...
 Verifying Application Signature...
 Initiating Application Install...
 ...

Note: in case you are not aware of:

• ISE 3.0 End of Support - July 13th, 2025
• ISE 3.2 End of Life Announcement - May 5th, 2025
• ISE 3.2.0 parity with ISE 2.7 P7, 3.0 P6. and 3.1 P3.
• ISE 3.2 supports upgrade from: 2.7+.
• SNS 3595 is supported till ISE 3.2
• SNS 3515 is NOT supported in ISE 3.1+

Hope this helps !!!