ISE 1.2 to 1.3 upgrade clarification question

[bberry]

I am looking to upgrade from ISE version 1.2 to version 1. 3 and am reading through the upgrade guide. The basic steps they outline are to create a repository pointing to disk: and then run the application upgrade prepare using the new repository. They say the prepare should copy the file to the local repository and list the MD5 and SHA256 checksum.

Do I not need to "copy" the file to the server before the prepare or is there a different format for specifying the file on the prepare step? It seems this is looking for a local copy instead on on my FTP server but any format I use to try to specify my FTP server is not working.

The documentation simply gives application upgrade prepare {filename} {repository}.

Brent

[Kanwaljeet Singh]

Hi Brent,

To prepare upgrade you need to get the support bundle on the local disk.

conf t

repository local

url disk:/

exit

exit

copy ftp://<repository_url>/ ise-upgradebundle-1.2.x-to-1.3.0.###.x86_64.tar.gz disk:/

• To upgrade using this file, use the following command:
• application upgrade ise-upgradebundle-1.2.x-to-1.3.0.###.x86_64.tar.gz local

You can use prepare to put the file in local repository that you created and then use proceed to upgrade.

Also, visit this link for upgrade details:

https://supportforums.cisco.com/blog/12341806/upgrading-identity-services-engine-ise-13

Regards,

Kanwal

Note: Please mark answers if they are helpful.

[bberry]

This is the doc that I have to follow...

http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/upgrade_guide/b_ise_upgrade_guide_13.pdf

Page 15 (printed page 5) discusses creating a repository and copying local and gives the example but mentions the application upgrade prepare copies to disk and extracts.

Then on page 20 (printed 10) they go through the process of creating a repository and then running the application upgrade prepare command but it looks like they use a local copy. Nowhere have I seen the application upgrade prepare command pull from the remote repository at the same time as do the extraction in the document.

I was thinking maybe they wanted the repository created through the CLI to be where files were extracted as that is deleted when the system reloads or at least that is what the messages says. Not sure how that applies since this point to disk and I do not think that would be deleted.

Brent