Cisco Prime 2.0 upgrade to CPI 2.1 process

Document

Thu, 01/29/2015 - 02:13
Sep 17th, 2014
User Badges:
  • Cisco Employee,

Introduction

Cisco Prime 2.0 upgrade to CPI 2.1 process

More Information

You can upgrade the following Cisco Prime Infrastructure (and predecessor) products to Cisco Prime Infrastructure 2.1:

  • Cisco Prime Infrastructure 2.0.0.0.294
  • Cisco Prime Infrastructure 1.3.0.20

If you are using a version earlier than 1.3.0.20, see the instructions for upgrading your software to version 2.0 provided in the Cisco Prime Infrastructure 2.0 Quick Start Guide . There is no upgrade path from version 1.4.x to version 2.1 at present.

Before attempting to upgrade to 2.1, make sure that you download the appropriate patch listed in Table 7 . and then install it using the instructions in Installing Patches . Once you have installed the appropriate patches, you will also need to take a new application backup before performing a system migration or inline upgrade.

 

 Critical Point Patches
If you are using...
Install this patch before upgrading...

Prime Infrastructure 1.3.0.20 (includes 1.3.0.20-2)

PI_1_3_0_20-Update.4-16.tar.gz

 

Once patched, you can upgrade these versions to 2.1 using either of the following methods:

1. System Migration —Install Cisco Prime Infrastructure 2.1 as a new system on a new host, and restore the existing system’s data to the new host. You can then decommission the old host. This option is preferred if you want to migrate to a larger OVA, have a large network, or cannot afford service downtime. For details, see Migrating to a New System .

2. Inline Upgrade —Upgrades your existing system to version 2.1. All existing data is retained and you will be using the same size OVA when the upgrade is complete. The existing product will not be operational until the upgrade is complete. This option is preferred when you want to keep the same size OVA and service downtime during the upgrade is acceptable. For details, see Performing an Inline Upgrade .

Prime Infrastructure application backups include license data. Reinstalling on a new system or virtual machine does not require you to rehost your licenses, so long as you use a recent application backup to restore your license data from the old system to the upgraded system . In any other case, you must email a request to [email protected] to rehost your licenses. You will need to Include your VUDI details and existing license details, including the number of licenses in your request.

Checking current Version

 

CPI20/admin# show ver

Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.6.003-px-build
ADE-OS System Architecture: x86_64

Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: CPI20

Version information of installed applications
---------------------------------------------

Cisco Prime Infrastructure
------------------------------------------
Version : 2.0.0.0.294  --------------------------<<<
CPI20/admin#

Transfer Patch file into the CPI defaultRepo

 

copy tftp://10.x.x.x/PI-Upgrade-2.1.0.0.87.tar.gz disk:/defaultRepo

Checking the defaultRepo

CPI20/admin# show repository defaultRepo
CPI20-140806-0330.tar.gpg
CPI20-140813-0330.tar.gpg
PI-Upgrade-2.1.0.0.87.tar.gz  -------------------<<< This file should be present in the defaulRepo before starting the Upgrade
CPI20/admin#


Stoping NCS Services before upgrade

 

CPI20/admin# ncs stop

Stopping Network Control System...

This may take a few minutes...

Network Control System successfully shutdown.

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

Stop of Plug and Play Gateway Completed!!
SAM daemon process id does not exist
DA daemon process id does not exist
DA syslog daemon process id does not exist

 

Upgrade process

CPI20/admin# application upgrade PI-Upgrade-2.1.0.0.87.tar.gz defaultRepo
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 ...

[WARNING] System will reboot after a successful installation of this package (after Stage 7).
After reboot, please login again into the server to check status.
No action required at this time. Continuing with Stage 3.

% Repository not found  -- complete.
  Stage 4 of 7: Upgrading binaries ...
  -- complete.
  Prime Infrastructure Application installation completed
          

  Stage 5 of 7: Retrieving system version ...
  -- 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: 2014-08-15 00:21:25.162, Time Taken : 0 hr, 0 min, 17 sec
                  Stage 2 of 5: Schema Upgrade ...
                                : This could take long time based on the existing data size.
                                        -- completed at: 2014-08-15 00:24:56.716, Time Taken : 0 hr, 3 min, 31 sec
                  Stage 3 of 5: Post Migration Schema Upgrade ...
                                        -- completed at: 2014-08-15 00:26:34.534, Time Taken : 0 hr, 1 min, 37 sec
                  Stage 4 of 5: Enabling DB Constraints ...
                                        -- completed at: 2014-08-15 00:34:31.834, Time Taken : 0 hr, 7 min, 56 sec
                  Stage 5 of 5: Finishing Up ...
                                        -- completed at: 2014-08-15 00:34:44.867, Time Taken : 0 hr, 0 min, 13 sec
  -- complete.
  Stage 7 of 7: Re-enabling Database Settings ...
  -- complete.
Upgrade Finished. Server is  restarting . Please wait ..

% This application Install or Upgrade requires reboot, rebooting now...

Broadcast message from root (pts/0) (Fri Aug 15 00:38:13 2014):

The system is going down for reboot NOW!

Application upgrade successful


Checking the Code after upgrading

 

CPI20/admin# show version

Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.6.003-px-build
ADE-OS System Architecture: x86_64

Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: CPI20

Version information of installed applications
---------------------------------------------

Cisco Prime Infrastructure
------------------------------------------
Version : 2.1.0.0.87   -----------------------------<<<<< Upgraded Version
CPI20/admin#

 

Tip: the self-signed certificate will not be migrated u need to create a new CSR and import the cert again.

Reference

Loading.
Sebastian Helmer Fri, 12/12/2014 - 13:53
User Badges:
  • Silver, 250 points or more

That works great. 

 

One thing to add, the self-signed certificate will not be migrated u need to create a new CSR and import the cert again.

 

donglei888999 Tue, 01/27/2015 - 01:23
User Badges:

HI Sebastian, 

 

May I know how to create a new CSR and import? can you show the steps?

Sebastian Helmer Tue, 01/27/2015 - 07:49
User Badges:
  • Silver, 250 points or more

yepp, it is also in the cisco doc. I worked with an internal CA and colleauges they know how to work with that. so I just requested the necessary files.

 

ncs key genkey -newdn -csr mycert repository myrepo

copy the mycert file to your CA and get the CA back. Copy all certificates together for a chain which needs to be imported in the following order

 

-----BEGIN CERTIFICATE-----

*Device cert*

-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----

*Intermediate CA cert *

-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----

*Root CA cert *

-----END CERTIFICATE-----

Additional u need the p7b file from your CA which contains the chain.

Import Certificate

Import cer

ncs key importcacert mycert.cer mycert.cer reporitory myrepo

ncs stop

ncs start

The restart is necessary before u import the p7b file. Otherwise u get an error message

Import p7b file

ncs key importsignedcert mycert.p7b repository myrep

 

ncs stop

ncs start

 

Thanks it!"
 

 

 

 

donglei888999 Tue, 01/27/2015 - 18:07
User Badges:

Hi Sabasitian,

Sorry, I cannot find the cisco docs that shows how to import the certification, can you pls show me the links?  Appreciated!

Actions

This Document

 

 

Trending Topics - Security & Network