Cisco Prime 3.10.1 > 3.10.2 Issues

[Moudar]

Hi, 

Trying to upgrade Prime from 3.10.1 to 3.10.2

The problem is the the 3.10.2 file is .gz file and Prime does not accept it.

So when trying to upload that file into Prime i get this:

So, what do I miss here?

[DanielP211 · Accepted solution]

Hello!

The file is correct. I would recommend you to do the upgrade from CLI. I'm not sure if it works over GUI directly, that is intended more for patches. With the following steps:
- Copy the verified upgrade file to the default repository - defaultRepo (use SCP, first generate the SCP user with the script getSCPcredentials.sh - location is /opt/CSCOlumos/bin/)
- Stop the Prime Infrastructure server by entering the command ncs stop
- Run: application upgrade PI-Upgrade-3.10.x_to_3.10.2-0.0.90.tar.gz defaultRepo
- After upgrade check: ncs status

Don't forget to install the necesary patch after upgrade (PI_3_10_2_SystemPatch-1.0.5.ubf).

BR

[Moudar]

That process took about 3 hours! to complete. I wonder why only 3.10.2 needs installing through CLI?

It looked like this:

prime-10/admin# application upgrade PI-Upgrade-3.10.x_to_3.10.2-0.0.90.tar.gz TFTP-1
Save the current ADE-OS running configuration? (yes/no) [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] ?

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 ...
  -- complete.
  Stage 4 of 7: Upgrading binaries ...
  -- complete.
  Prime Application installation completed
Note: Forwarding request to 'systemctl disable ipmi.service'.
            Stage 5 of 7: Executing post-install ...


Just before calling dbadmin.sh Upgrade
  -- complete.
  Stage 6 of 7: Updating Database Schema ...
              : This could take long time based on the existing data size.
                  Stage 1 of 5: Pre Migration Schema Upgrade ...
                                        -- completed at: 2024-02-15 14:33:54.237, Time Taken : 0 hr, 8 min, 24 sec
                  Stage 2 of 5: Schema Upgrade ...




                                        -- completed at: 2024-02-15 15:24:43.685, Time Taken : 0 hr, 50 min, 48 sec
                  Stage 3 of 5: Post Migration Schema Upgrade ...
                                        -- completed at: 2024-02-15 15:41:35.215, Time Taken : 0 hr, 16 min, 50 sec
                  Stage 4 of 5: Enabling DB Constraints ...
                                        -- completed at: 2024-02-15 15:41:52.188, Time Taken : 0 hr, 0 min, 15 sec
                  Stage 5 of 5: Finishing Up ...
                                        -- completed at: 2024-02-15 15:42:13.939, Time Taken : 0 hr, 0 min, 20 sec
  -- complete.
  Stage 7 of 7: Re-enabling Database Settings ...
  -- complete.
Upgrade Finished. Server is  restarting . Please wait ..
INFO: Mount point exists!

% This application Install or Upgrade requires reboot, rebooting now...
Connection reset by 10.32.0.149 port 22