Cisco Prime Infrastructure – Update from 2.1 to 2.2

Tutorial on how to upgrade your Prime Infrastructure to 2.2

Home / Posts / 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

    1
    2
    3
    
    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.

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    
    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.

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    
    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

    1
    2
    3
    
    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!

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    
    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

     

    comments powered by Disqus
    Built with Hugo
    Theme Stack designed by Jimmy