Upgrade Cisco Prime Infrastructure 2.1.1 to 2.2

[nazir.haron]

Hi,

I would like to know how to

1. Upgrade Cisco Prime Infrastucture 2.1.1 to 2.2 procedure

2. How to backup existing config and data

Thanks in advance

- nazir

[Marvin Rhoads]

I saw similar results recently - restore (onto PI 3.0) took 5 hr 18 min while the backup (from PI 2.2) took 2 hr 56 min:

VM-PI-V3/admin# show restore log
Started at : Fri Dec 11 17:30:00 2015
Initiating restore. Please wait...
 Restore Started at 12/11/15 17:30:00
 Stage 1 of 9: Transferring backup file ... 
 -- completed at 12/11/15 17:36:56
 Stage 2 of 9: Decrypting backup file ...
 -- completed at 12/11/15 18:12:21
 Stage 3 of 9: Unpacking backup file ...
 -- completed at 12/11/15 18:17:01
 Stage 4 of 9: Decompressing backup ...
 -- completed at 12/11/15 18:19:55
 Stage 5 of 9: Restoring Support Files ...
 -- completed at 12/11/15 18:19:58
 Stage 6 of 9: Restoring Database Files ...
 -- completed at 12/11/15 18:20:43
 Stage 7 of 9: Recovering Database ...
 -- completed at 12/11/15 20:15:06
 Stage 8 of 9: Updating Database Schema ...
 Stage 1 of 5: Pre Migration Schema Upgrade ...
 -- completed at: 2015-12-11 21:30:57.059, Time Taken : 1 hr, 3 min, 43 sec
 Stage 2 of 5: Schema Upgrade ...
 : This could take long time based on the existing data size.
 -- completed at: 2015-12-11 21:37:14.576, Time Taken : 0 hr, 6 min, 17 sec
 Stage 3 of 5: Post Migration Schema Upgrade ...
 -- completed at: 2015-12-11 21:42:22.633, Time Taken : 0 hr, 5 min, 7 sec
 Stage 4 of 5: Enabling DB Constraints ...
 -- completed at: 2015-12-11 21:45:42.483, Time Taken : 0 hr, 3 min, 6 sec
 Stage 5 of 5: Finishing Up ...
 -- completed at: 2015-12-11 21:46:17.681, Time Taken : 0 hr, 0 min, 35 sec
 -- completed at 12/11/15 21:46:43
 Stage 9 of 9: Re-enabling Database Settings ...
 -- completed at 12/11/15 22:48:33
 Total Restore duration is: 05h:18m:33s
INFO: Restore completed successfully.
Starting Prime Infrastructure...
This may take a while (10 minutes or more) ...
VM-PI-V3/admin#

VM-PI/admin# backup TAC repository defaultRepo application NCS
DO NOT press ^C while the backup is in progress
Aborting backup with a ^C may terminate the backup operation or the backup file may be corrupted
Checking for arhivelog cleanup job
 Backup Started at : 12/11/15 08:55:20
 Stage 1 of 7: Database backup ...
 Database size: 533G
-- completed at 12/11/15 10:23:31
 Stage 2 of 7: Database copy ...
 -- completed at 12/11/15 10:23:31
 Stage 3 of 7: Backing up support files ...
 -- completed at 12/11/15 10:23:50
 Stage 4 of 7: Compressing Backup ...
 -- completed at 12/11/15 10:24:12
 Stage 5 of 7: Building backup file ...
 -- completed at 12/11/15 11:20:40
 Stage 6 of 7: Encrypting backup file ...
 -- completed at 12/11/15 11:44:40
 Stage 7 of 7: Transferring backup file ...
 -- completed at 12/11/15 11:51:26
% Backup file created is: TAC-151211-0855__VER2.2.0.0.158_BKSZ532G_CPU16_MEM4G_RAM15G_SWAP15G_APP_CK2658036083.tar.gpg 
 Total Backup duration is: 2h:56m:6s
VM-PI/admin#

[AFROJ AHMAD]

it should not take much time ,however I would suggest not to interrupt it ,as you are not getting any error.

Thanks-

[jacky.reinbold]

In my case I had two different customers needing an Upgrade from CPI 2.1 to 2.2

- First Customer: I had first to resolve update files issues on CPI 2.1 (updates no installed issue) before I've been able to do a backup.  After that all backup/restore operations have worked as expected on CPI 2.2, ..., and the maps with the APs were present again

- Second customer:  backup/restore on CPI 2.2 ok, but no more APs on the campus map (maps already present).  A map export/reimport in CPI 2.2 did not help.  The customer has to position again manually 116 APs in the campus maps.

Recommendations:

- make a cpmplete map export before shuting down the old cpi 2.1

- don't delete it an give it another IP, in case you need it again

- don't install the technology packs on cpi 2.2, because you will not be able to update update/bugfix packages anymore (PI 2.2.2 and further service packs cannot be installed if DC package is installed)

[Abnerblas22]

Someone made ​​a PI 3.0 restored from the backup IP NCS1.x ?

[AFROJ AHMAD]

Nope, it won't work as it is not supported:

http://www.cisco.com/web/software/284272933/130096/Guide_for_installing_PI_3_0_and_migrating_PI_2_2_x_to_PI_3_0_2_on_a_Gen-1_Appliance.pdf

PI 3.0 Gen1 Upgrade
& Migration Supported Versions
Prime Infrastructure(PI) supportsupgrade and restoring from backups,for the following releases:

Prime Infrastructure versions 2.2, 2.2.1, 2.2.2 and 2.2.3

Prime
Infrastructure 2.2.1 Technology Packages:

Data Center Technology Package 1.0.0 for Cisco Prime Infrastructure 2.2.1

Wireless Technology Package 1.0.0 for Cisco Prime Infrastructure 2.2.1

Prime Infrastructure versions 2.2.x ,and any point patches (and /or up dates) related to PI 2.2.x that were posted on Cisco.com


Thanks-
Afroz
***Ratings Encourages Contributors ***

[Abnerblas22]

What is the best way to make the NCS upgade to PI 3.0?


Thanks
Abner Blas 

[Marvin Rhoads]

The best approach is to export your devices and maps and then import them onto a fresh installation of PI 3.1.

If you need to keep all the historical data, you can do the (many) upgrades necessary but it will probably take you several days, runs the risk of failing at some point and will generally be more trouble than it's worth.

Also, if you're currently on old hardware (Gen 1 appliance) then you cannot as the old hardware is not supported with the new software.

If after that you really want to upgrade vs. rebuild, then you need to upgrade NCS 1.1 (assuming it's at the necessary path level to Prime Infrastructure 1.3:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/1-3/release/notes/cpi_rn_13.html#pgfId-73605

..then 1.3 to 2.1:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1/quickstart/guide/cpi_qsg.html#pgfId-56675

then 2.1 to 2.2

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/quickstart/guide/cpi_qsg.html#pgfId-113783

then 2.2 to 3.0

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#pgfId-120990

and finally 3.0 to 3.1:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/quickstart/guide/cpi_qsg.html#pgfId-113783

(oh and then patch 3.1 to release 3.1.3 and apply the latest device pack)