02-24-2021 06:02 PM
I'm running Prime Infrastructure 3.7 and the inline upgrade failed as shown below.
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.02.24 17:04:19 =~=~=~=~=~=~=~=~=~=~=~=
application upgrade PI-Upgrade-36x_37x_to_3.8.0.0.310.tar.gz CCFTP
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Please ensure you have a backup of the system before proceeding.
Proceed with the application upgrade ? (yes/no) [yes] ? yes
DO NOT press ^C while the upgrade is in progress
Aborting upgrade with a ^C may leave the system in a unrecoverable state
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
*** System will reboot after a successful installation of this package ***
After reboot, please login again into the server to check status
Stage 3 of 7: Executing pre-install ...
[ERROR] This upgrade path is not supported. Please do a fresh installation of Prime Infrastructure 3.8 and restore either Prime Infrastructure 3.6 or 3.7 version backup. Refer the Cisco Prime Infrastructure 3.8 Administrator Guide section Backup and Restore.
% Pre-install step failed. Please check the logs for more details.
cc-prime/admin#
cc-prime/admin# show ver
Cisco Application Deployment Engine OS Release: 4.1
ADE-OS Build Version: 4.1.0.001
ADE-OS System Architecture: x86_64
Copyright (c) 2009-2019 by Cisco Systems, Inc.
All rights reserved.
Hostname: cc-prime
Version information of installed applications
---------------------------------------------
Cisco Prime Infrastructure
********************************************************
Version : 3.7.0 [FIPS not Enabled]
Build : 3.7.0.0.159
Have anyone experience this issue?
I don't have access to the VCenter to run a clean install and bring the backup.
02-24-2021 06:15 PM
Found my response here:
If your existing Prime Infrastructure is 3.6.x or 3.7.x, and your upgrade path contains 3.4.x or earlier versions, then you cannot in-line upgrade that server to Prime Infrastructure 3.8 due to security vulnerabilities in the underlying Red Hat 6 installation. You will need to take a backup of the Prime Infrastructure 3.6.x or 3.7.x server, deploy a fresh Prime Infrastructure 3.8 server, and restore that backup into the Prime Infrastructure 3.8 server.
02-24-2021 06:37 PM - edited 02-24-2021 06:37 PM
Funny that. Yesterday, I was attempting to do an inline upgrade from PI 3.7 to PI 3.9 and encountered the same message.
TAC was very swift with the response:
If your existing Prime Infrastructure is 3.6.x or 3.7.x, and your upgrade path contains 3.4.x or earlier versions, then you cannot in-line upgrade that server to Prime Infrastructure 3.8 due to security vulnerabilities in the underlying Red Hat 6 installation. You will need to take a backup of the Prime Infrastructure 3.6.x or 3.7.x server, deploy a fresh Prime Infrastructure 3.8 server, and restore that backup into the Prime Infrastructure 3.8 server.
In English, if your existing PI came from PI 3.4, then you will need to do a fresh install.
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