03-30-2017 01:29 AM - edited 03-11-2019 12:35 AM
Hello experts,
I am trying to upgrade the ISE version from 1.3 to 2.1.
1. download the new ise version "ise-upgradebundle-1.3.x-and-1.4.x-to-2.1.0.474.x86_64_old.tar.gz"
did the MD5 checksum and its showing diff then what cisco mentioned....
Cisco - md5: 35a159416afd0900c9da7b3dc6c72043
Mine - MD5: b29.....
What should i do now ??
Thanks
03-30-2017 03:28 AM
What location is the upgrade bundle on when you checked that md5 checksum?
If on your PC, try downlaod again - perhaps using a different browser.
If on the ISE server, please share how you transferred it to there.
Sometimes when moving things around via ftp, failure to specify binary transfer can result in corrupted files and the checksum being incorrect.
03-30-2017 04:38 AM
I said yes even-though it was showing wrong MD5 and its accepted and extracted the file successfully. Now its finished the upgrade...
ISE2/admin# application upgrade proceed
Initiating Application Upgrade...
% Warning: Do not use Ctrl-C or close this terminal window until upgrade completes.
-Checking VM for minimum hardware requirements
STEP 1: Stopping ISE application...
STEP 2: Verifying files in bundle...
-Internal hash verification passed for bundle
STEP 3: Validating data before upgrade...
STEP 4: Taking backup of the configuration data...
STEP 5: Running ISE configuration database schema upgrade...
- Running db sanity check to fix index corruption, if any...
- Upgrading Schema for UPS Model...
- Upgrading Schema completed for UPS Model.
ISE database schema upgrade completed.
STEP 6: Running ISE configuration data upgrade...
- Data upgrade step 1/95, CertReqMgmtBootstrapService(1.4.0.0)... Done in 2 seconds.
- Data upgrade step 2/95, NSFUpgradeService(1.4.0.110)... Done in 0 seconds.
- Data upgrade step 3/95, NSFUpgradeService(1.4.0.119)... Done in 0 seconds.
- Data upgrade step 4/95, NSFUpgradeService(1.4.0.125)... Done in 0 seconds.
- Data upgrade step 5/95, NSFUpgradeService(1.4.0.157)... Done in 0 seconds.
- Data upgrade step 6/95, GuestAccessUpgradeService(1.4.0.157)... Done in 10 seconds.
- Data upgrade step 7/95, NSFUpgradeService(1.4.0.164)... Done in 0 seconds.
- Data upgrade step 8/95, MDMPartnerUpgradeService(1.4.0.166)... Done in 0 seconds.
- Data upgrade step 9/95, MDMPartnerUpgradeService(1.4.0.167)... Done in 0 seconds.
- Data upgrade step 10/95, ProfilerUpgradeService(1.4.0.175)... Done in 1 seconds.
- Data upgrade step 11/95, CertMgmtUpgradeService(1.4.0.217)... Done in 0 seconds.
- Data upgrade step 12/95, UPSUpgradeHandler(1.5.0.136)... Done in 9 seconds.
- Data upgrade step 13/95, UPSUpgradeHandler(1.5.0.139)... Done in 0 seconds.
- Data upgrade step 14/95, ANCRegistration(1.5.0.140)... Done in 0 seconds.
- Data upgrade step 15/95, NSFUpgradeService(1.5.0.149)... Done in 10 seconds.
- Data upgrade step 16/95, UPSUpgradeHandler(1.5.0.150)... Done in 7 seconds.
- Data upgrade step 17/95, NetworkAccessUpgrade(1.5.0.151)... Done in 0 seconds.
- Data upgrade step 18/95, UPSUpgradeHandler(1.5.0.156)... Done in 0 seconds.
- Data upgrade step 19/95, NetworkAccessUpgrade(1.5.0.159)... Done in 0 seconds.
- Data upgrade step 20/95, NetworkAccessUpgrade(1.5.0.162)... Done in 0 seconds.
- Data upgrade step 21/95, NSFUpgradeService(1.5.0.180)... Done in 0 seconds.
- Data upgrade step 22/95, NetworkAccessUpgrade(1.5.0.180)... Done in 0 seconds.
- Data upgrade step 23/95, NetworkAccessUpgrade(1.5.0.181)... Done in 1 seconds.
- Data upgrade step 24/95, UPSUpgradeHandler(1.5.0.183)... Done in 0 seconds.
- Data upgrade step 25/95, NSFUpgradeService(1.5.0.184)... Done in 0 seconds.
- Data upgrade step 26/95, UPSUpgradeHandler(1.5.0.187)... Done in 1 seconds.
- Data upgrade step 27/95, NSFUpgradeService(1.5.0.199)... Done in 0 seconds.
- Data upgrade step 28/95, HostConfigUpgradeService(1.5.0.199)... Done in 4 seconds.
- Data upgrade step 29/95, NetworkAccessUpgrade(1.5.0.201)... Done in 0 seconds.
- Data upgrade step 30/95, NetworkAccessUpgrade(1.5.0.202)... Done in 0 seconds.
- Data upgrade step 31/95, GuestAccessUpgradeService(1.5.0.212)... Done in 1 seconds.
- Data upgrade step 32/95, NSFUpgradeService(1.5.0.234)... Done in 1 seconds.
- Data upgrade step 33/95, UPSUpgradeHandler(1.5.0.244)... Done in 0 seconds.
- Data upgrade step 34/95, NSFUpgradeService(1.5.0.246)... Done in 0 seconds.
- Data upgrade step 35/95, AuthzUpgradeService(1.5.0.252)... Done in 0 seconds.
- Data upgrade step 36/95, NSFUpgradeService(1.5.0.257)... Done in 0 seconds.
- Data upgrade step 37/95, NetworkAccessUpgrade(2.0.0.131)... Done in 0 seconds.
- Data upgrade step 38/95, AuthzUpgradeService(2.0.0.151)... Done in 0 seconds.
- Data upgrade step 39/95, AuthenPolicyUpgradeService(2.0.0.151)... Done in 0 seconds.
- Data upgrade step 40/95, NadProfilePolicyElemUpgradeService(2.0.0.151)... Done in 11 seconds.
- Data upgrade step 41/95, NetworkAccessUpgrade(2.0.0.154)... Done in 0 seconds.
- Data upgrade step 42/95, NetworkAccessUpgrade(2.0.0.156)... Done in 0 seconds.
- Data upgrade step 43/95, NSFUpgradeService(2.0.0.159)... Done in 0 seconds.
- Data upgrade step 44/95, ProvisioningUpgradeService(2.0.0.166)... Done in 1 seconds.
- Data upgrade step 45/95, CADeploymentUpgradeService(2.0.0.190)... Done in 13 seconds.
- Data upgrade step 46/95, NSFUpgradeService(2.0.0.194)... Done in 0 seconds.
- Data upgrade step 47/95, CertMgmtUpgradeService(2.0.0.212)... Done in 1 seconds.
- Data upgrade step 48/95, NSFUpgradeService(2.0.0.220)... Done in 4 seconds.
- Data upgrade step 49/95, NSFUpgradeService(2.0.0.244)... Done in 0 seconds.
- Data upgrade step 50/95, NSFUpgradeService(2.0.0.245)... Done in 0 seconds.
- Data upgrade step 51/95, EPSRegistration(2.0.0.262)... Done in 0 seconds.
- Data upgrade step 52/95, NSFUpgradeService(2.0.0.268)... Done in 0 seconds.
- Data upgrade step 53/95, UPSUpgradeHandler(2.0.0.271)... Done in 0 seconds.
- Data upgrade step 54/95, AuthzUpgradeService(2.0.0.308)... Done in 0 seconds.
- Data upgrade step 55/95, NSFUpgradeService(2.1.0.102)... Done in 0 seconds.
- Data upgrade step 56/95, UPSUpgradeHandler(2.1.0.105)... Done in 22 seconds.
- Data upgrade step 57/95, UPSUpgradeHandler(2.1.0.107)... Done in 2 seconds.
- Data upgrade step 58/95, NSFUpgradeService(2.1.0.109)... Done in 0 seconds.
- Data upgrade step 59/95, NSFUpgradeService(2.1.0.126)... Done in 0 seconds.
- Data upgrade step 60/95, NetworkAccessUpgrade(2.1.0.127)... Done in 0 seconds.
- Data upgrade step 61/95, ProfilerUpgradeService(2.1.0.134)... Done in 0 seconds.
- Data upgrade step 62/95, ProfilerUpgradeService(2.1.0.139)... Done in 0 seconds.
- Data upgrade step 63/95, ProfilerUpgradeService(2.1.0.166)... Done in 49 seconds.
- Data upgrade step 64/95, NSFUpgradeService(2.1.0.168)... Done in 0 seconds.
- Data upgrade step 65/95, AlarmsUpgradeHandler(2.1.0.169)... Done in 1 seconds.
- Data upgrade step 66/95, RegisterPostureTypes(2.1.0.180)... Done in 1 seconds.
- Data upgrade step 67/95, RegisterPostureTypes(2.1.0.189)... Done in 0 seconds.
- Data upgrade step 68/95, UPSUpgradeHandler(2.1.0.194)... Done in 0 seconds.
- Data upgrade step 69/95, TrustsecWorkflowRegistration(2.1.0.203)... Done in 0 seconds.
- Data upgrade step 70/95, NSFUpgradeService(2.1.0.205)... Done in 0 seconds.
- Data upgrade step 71/95, NetworkAccessUpgrade(2.1.0.207)... Done in 0 seconds.
- Data upgrade step 72/95, NSFUpgradeService(2.1.0.212)... Done in 0 seconds.
- Data upgrade step 73/95, NetworkAccessUpgrade(2.1.0.241)... Done in 0 seconds.
- Data upgrade step 74/95, NetworkAccessUpgrade(2.1.0.242)... Done in 0 seconds.
- Data upgrade step 75/95, UPSUpgradeHandler(2.1.0.244)... Done in 0 seconds.
- Data upgrade step 76/95, ProfilerUpgradeService(2.1.0.248)... Done in 0 seconds.
- Data upgrade step 77/95, NetworkAccessUpgrade(2.1.0.254)... Done in 0 seconds.
- Data upgrade step 78/95, UPSUpgradeHandler(2.1.0.255)... Done in 7 seconds.
- Data upgrade step 79/95, MDMPartnerUpgradeService(2.1.0.257)... Done in 0 seconds.
- Data upgrade step 80/95, NetworkAccessUpgrade(2.1.0.258)... Done in 0 seconds.
- Data upgrade step 81/95, ProfilerUpgradeService(2.1.0.258)... .Done in 70 seconds.
- Data upgrade step 82/95, MDMPartnerUpgradeService(2.1.0.258)... Done in 0 seconds.
- Data upgrade step 83/95, UPSUpgradeHandler(2.1.0.279)... Done in 0 seconds.
- Data upgrade step 84/95, NSFUpgradeService(2.1.0.282)... Done in 0 seconds.
- Data upgrade step 85/95, NetworkAccessUpgrade(2.1.0.288)... Done in 0 seconds.
- Data upgrade step 86/95, NetworkAccessUpgrade(2.1.0.295)... Done in 0 seconds.
- Data upgrade step 87/95, CertMgmtUpgradeService(2.1.0.296)... Done in 0 seconds.
- Data upgrade step 88/95, NetworkAccessUpgrade(2.1.0.299)... Done in 0 seconds.
- Data upgrade step 89/95, NetworkAccessUpgrade(2.1.0.322)... Done in 0 seconds.
- Data upgrade step 90/95, NetworkAccessUpgrade(2.1.0.330)... Done in 0 seconds.
- Data upgrade step 91/95, NSFUpgradeService(2.1.0.353)... Done in 0 seconds.
- Data upgrade step 92/95, ProfilerUpgradeService(2.1.0.354)... Done in 0 seconds.
- Data upgrade step 93/95, NSFUpgradeService(2.1.0.474)... Done in 0 seconds.
- Data upgrade step 94/95, ProfilerUpgradeService(2.1.0.474)... Done in 1 seconds.
- Data upgrade step 95/95, GuestAccessUpgradeService(2.1.0.474)... Done in 9 seconds.
STEP 7: Running ISE configuration data upgrade for node specific data...
STEP 8: Running ISE M&T database upgrade...
ISE M&T Log Processor is not running
ISE database M&T schema upgrade completed.
% NOTICE: The appliance will reboot twice to upgrade software and ADE-OS. During this time progress of the upgrade is visible on console. It could take up to 30 minutes for this to complete.
Rebooting to do Identity Service Engine upgrade...
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide
Thanks marvin..
What location is the upgrade bundle on when you checked that md5 checksum?
its was in my local drive C
If on your PC, try download again - perhaps using a different browser.
I tried with IE and Chrome.....same result
If on the ISE server, please share how you transferred it to there.
via FTP ( even after transfer its showing the same MD5)
Sometimes when moving things around via ftp, failure to specify binary transfer can result in corrupted files and the checksum being incorrect.