Cisco Prime Infrastructure – Update from 2.1 to 2.2

 Overview

I did the Upgrade from Prime Infrastructure 2.1 to Prime Infrastructure 2.2 last week for one of our customers. Unfortunately this upgrade isn’t possible ‘in place’, you have to install a new Prime Infrastructure 2.2 Server and then import your old configuration.

As described in the Prime Infrastructure 2.2 Quickstart Guide you have to be on one of the following versions that the backup can be used in 2.2:

  • Cisco Prime Infrastructure 2.1.2 (with the UBF patch)
  • Cisco Prime Infrastructure 2.1.1 (with the UBF patch)
  • Cisco Prime Infrastructure 2.1.0.0.87
  • Cisco Prime Infrastructure 1.4.2
  • Cisco Prime Infrastructure 1.4.1
  • Cisco Prime Infrastructure 1.4.0.45

Luckily we were on 2.1.0.0.87, so it wasn’t necessary to do a minor upgrade first.

 Install a Prime Infrastructure 2.2 Server

First you need a new Server, for me this was again a VM (like the 2.1 installation)
You can download the Image here, just pick the right one for your case. For me it was:
Cisco Prime Infrastructure 2.2 Virtual Appliance
PI-VA-2.2.0.0.158.ova

If you also use the VM, check the different Virtual Appliance options out in this table:
Cisco Prime Infrastructure 2.2 VM Scaleing

This should help you to pick the right VM.

Now you can just install the image through the vsphere console and finish the basic setup. I used a different IP first and changed it before i did the restore.

Backup of your Prime Infrastructure 2.1

After you ensured that you have one of the compatible versions, you start with the backup.
The easiest way is to use a remote repository, just configure one from the CLI like these

repository ftp
 url ftp://your.ftp.server/path/
 user username password plain plain

You’re now ready to perform the backup, this took some time for me.

sv00019/admin# backup PI_Backup repository ftp application NCS
% Creating backup with timestamped filename: PI_Backup-150430-1120.tar.gpg
 Backup Started at : 04/30/15 11:20:29
 Stage 1 of 7: Database backup ...
 Database size: 81G
 -- completed at 04/30/15 11:37:09
 Stage 2 of 7: Database copy ...
 -- completed at 04/30/15 11:37:09
 Stage 3 of 7: Backing up support files ...
 -- completed at 04/30/15 11:37:17
 Stage 4 of 7: Compressing Backup ...
 -- completed at 04/30/15 11:37:29
 Stage 5 of 7: Building backup file ...
 -- completed at 04/30/15 11:47:04
 Stage 6 of 7: Encrypting backup file ...
 -- completed at 04/30/15 11:50:01
 Stage 7 of 7: Transferring backup file ...
 -- completed at 04/30/15 11:51:32
 Total Backup duration is: 0h:31m:3s

After that, you are ready to restore the Backup.

Restore the Backup of your Prime Infrastructure 2.1

We assume here that your new Prime Infrastructure 2.2 Server is ready. First step would be to shut down the 2.1 Server and configure this IP on the 2.2 Server.


sv00283/admin# application stop NCS

Stopping Prime Infrastructure...

This may take a few minutes...

Prime Infrastructure successfully shutdown.


Plug and Play Gateway is being shut down..... Please wait!!!

Stop of Plug and Play Gateway Completed!!
Stopping SAM daemon...
Checking for SAM daemon again ...
SAM Daemon not found...
Stopping DA daemon ...
Checking for DA daemon again ...
DA Daemon not found...
Stopping strongSwan IPsec...


sv00283/admin(config)# interface GigabitEthernet 0
sv00283/admin(config-GigabitEthernet)# ip address 10.192.2.30 255.255.255.0

Changing the hostname or IP may result in undesired side effects,
such as installed application(s) being restarted.
Are you sure you want to proceed? [y/n] y

I stopped the application first, just prevent any possible issues.
Then i added the same remote repository as i used for the backup

repository ftp
url ftp://your.ftp.server/path/
user username password plain plain

After this step, you are ready for the restore. Plan some time for this to finish!


sv00283/admin# restore PI_Backup-150430-1120.tar.gpg repository nas001 application NCS

* NOTE *
If the system console is disconnected or got cleared on session timeout
run 'show restore log' to see the output of the last restore session.

Restore will restart the application services. Continue? (yes/no) [yes] ?

DO NOT press ^C while the restoration is in progress
Aborting restore with a ^C may leave the system in a unrecoverable state

Initiating restore. Please wait...
Restore Started at 04/30/15 14:10:47
Stage 1 of 9: Transferring backup file ...
-- completed at 04/30/15 14:11:58
Stage 2 of 9: Decrypting backup file ...
-- completed at 04/30/15 14:16:04
Stage 3 of 9: Unpacking backup file ...
-- completed at 04/30/15 14:16:05
Stopping strongSwan IPsec failed: starter is not running
Stage 4 of 9: Decompressing backup ...
-- completed at 04/30/15 14:17:10
Stage 5 of 9: Restoring Support Files ...
-- completed at 04/30/15 14:17:12
Stage 6 of 9: Restoring Database Files ...
-- completed at 04/30/15 14:17:45
Stage 7 of 9: Recovering Database ...
-- completed at 04/30/15 15:13:01
Stage 8 of 9: Updating Database Schema ...
Stage 1 of 5: Pre Migration Schema Upgrade ...
-- completed at: 2015-04-30 15:38:25.126, Time Taken : 0 hr, 19 min, 10 sec
Stage 2 of 5: Schema Upgrade ...
: This could take long time based on the existing data size.
-- completed at: 2015-04-30 15:41:42.862, Time Taken : 0 hr, 3 min, 17 sec
Stage 3 of 5: Post Migration Schema Upgrade ...
-- completed at: 2015-04-30 16:04:13.639, Time Taken : 0 hr, 22 min, 30 sec
Stage 4 of 5: Enabling DB Constraints ...
-- completed at: 2015-04-30 16:04:34.163, Time Taken : 0 hr, 0 min, 12 sec
Stage 5 of 5: Finishing Up ...
-- completed at: 2015-04-30 16:04:41.941, Time Taken : 0 hr, 0 min, 7 sec
-- completed at 04/30/15 16:06:03
Stage 9 of 9: Re-enabling Database Settings ...
-- completed at 04/30/15 16:06:03
Total Restore duration is: 01h:55m:16s
INFO: Restore completed successfully.
Starting PI Server... This may take some time

Starting Prime Infrastructure...

This may take a while (10 minutes or more) ...

Prime Infrastructure started successfully.

Starting strongSwan 5.0.1 IPsec [starter]...

And that’s it, you are running now Prime Infrastructure 2.2

Cisco Prime Infrastructure 2.2 Login Screen

 

Related Posts

7 thoughts on “Cisco Prime Infrastructure – Update from 2.1 to 2.2

  1. Hi,
    I am in process of you testing upgrade from 2.1 to 2.2 in my lab. I just created the backup and found a strange thing. When the backup started, it mentioned the database size to be 56GB. However, once the backup completed, the file on ftp was only 800MB. Pasting the snapshot. Is it supposed to be like this? Do I just restore this exact file to the new VM PI 2.2.
    backup PI_Backup repository ftpserver 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
    Backup Started at : 06/30/15 09:56:10
    Stage 1 of 7: Database backup …
    Database size: 56G
    — completed at 06/30/15 10:03:29
    Stage 2 of 7: Database copy …
    — completed at 06/30/15 10:03:29
    Stage 3 of 7: Backing up support files …
    — completed at 06/30/15 10:03:32
    Stage 4 of 7: Compressing Backup …
    — completed at 06/30/15 10:03:35
    Stage 5 of 7: Building backup file …
    — completed at 06/30/15 10:04:42
    Stage 6 of 7: Encrypting backup file …
    — completed at 06/30/15 10:05:08
    Stage 7 of 7: Transferring backup file …
    — completed at 06/30/15 10:06:27
    % Backup file created is: PI_Backup-150630-0956__VER2.2.0.0.158_BKSZ55G_FIPS_ON_CPU4_MEM4G_RAM11G_SWAP15G_APP_CK3880690046.tar.gpg
    Total Backup duration is: 0h:10m:17s
    Thanks

    • Hi Jay,

      Great to hear from you!
      I just checked my backup file that was created, it has a size of 7.64GB from a DB Size of 81G.

      You just restore the backup file on the new PI 2.2 Instance, correct.
      This should work fine if there was no error during the backup process.

      Regards
      Richard

  2. Thanks for your reply Richard.

    This means compression significantly reduces the file size. Also, mine is a lab scenario with only 2 devices and 1 client. So there won’t be much data and I guess that’s why the DB has been compressed so much.

    Many thanks,
    Jay

  3. Hi Richardstrnad,

    Thank you so much for the information. I am going to help customer to upgrade from PI-2.1.1 to 2.2 tomorrow. These information are very helpful. Best wishes.

    But, there are two strange phenomenons on PI GUI, When I need to edit device/ add device on the page Device Work Center
    Operate->Device Work Center

    1.No any response when i click Add Device
    2. When i select the device and click Edit
    [msg showed on device details]
    There was an error while parsing and rendering the content. (Could not load class ‘dojoc.layout.AccordionDynamic’. Did you spell the name correctly and use a full path, like ‘dijit.form.Button’?)

    Thanks a lot.

    Pat

  4. HI Richard,

    Great blog – I have recently completed an upgrade from 2.1 to 2.2 moving from a Gen 1 appliance onto a Gen 2 appliance and the process worked seamlessly.

    Can you also tell me what plugin you use for your social icons?

    Thanks
    Roger

Leave a Reply

Your email address will not be published. Required fields are marked *