Upgrading NCS 1.1.1.24 to PI 1.2.1

Did anyone experience this?
Original running NCS 1.1.1.24 and upgraded to 1.1.2.12 with NCS-upgrade-bundle-1.1.2.12.gz in hopes to upgrade to PI 1.2.1 later.
1. Trying to upgrade with application upgrade ncs_patch-1.1.1.24-upgrade-12.gz wireless-nms-ftp
ncs/admin# application upgrade ncs_patch-1.1.1.24-upgrade-12.gz wireless-nms-ftp
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
6 [6049]: application:install cars_install.c[245] [admin]: Install initiated with bundle - ncs_patch-1.1.1.24-upgrade-12.gz, repo - wireless-nms-ftp
6 [6049]: application:install cars_install.c[259] [admin]: Stage area - /storeddata/Installing/.1358124802
6 [6049]: application:install cars_install.c[263] [admin]: Getting bundle to local machine
Stage 1 of 7: Transferring file ...
6 [6049]: transfer: cars_xfer.c[54] [admin]: ftp copy in of ncs_patch-1.1.1.24-upgrade-12.gz requested
7 [6049]: transfer: cars_xfer_util.c[92] [admin]: ftp get source - ncs_patch-1.1.1.24-upgrade-12.gz
7 [6049]: transfer: cars_xfer_util.c[93] [admin]: ftp get destination - /storeddata/Installing/.1358124802/ncs_patch-1.1.1.24-upgrade-12.gz
7 [6049]: transfer: cars_xfer_util.c[112] [admin]: initializing curl
7 [6049]: transfer: cars_xfer_util.c[125] [admin]: full url is ftp://132.234.254.29/ncs_patch-1.1.1.24-upgrade-12.gz
-- complete.
6 [6049]: application:install cars_install.c[278] [admin]: Got bundle at - /storeddata/Installing/.1358124802/ncs_patch-1.1.1.24-upgrade-12.gz
Stage 2 of 7: Unpacking file ...
6 [6049]: application:install cars_install.c[288] [admin]: Unbundling package ncs_patch-1.1.1.24-upgrade-12.gz
-- complete.
6 [6049]: application:install cars_install.c[306] [admin]: Unbundling done. Verifying input parameters...
6 [6049]: application:install cars_install.c[328] [admin]: Manifest file is at - /storeddata/Installing/.1358124802/manifest.xml
6 [6049]: application:install cars_install.c[338] [admin]: Manifest file appname - NCS
7 [6049]: application:install cars_install.c[152] [admin]: UPGRADE: Comparing app version, installed: 1.1.2.12-1, new = 1.1.1.24-1
4 [6049]: application:install cars_install.c[162] [admin]: UPGRADE: new version: 1.1.1.24-1 is older than the current version: 1.1.2.12-1
3 [6049]: application:install cars_install.c[361] [admin]: UPGRADE: Install aborted because version is the same or older than the current version
% Install package is older than the currently installed version. Remove first if downgrade is desired.
6 [6049]: application:install install_cli.c[173] [admin]: error message: Install package is older than the currently installed version. Remove first if downgrade is desired.
3 [6049]: application:install install_cli.c[177] [admin]: Error while Installing - Application bundle: ncs_patch-1.1.1.24-upgrade-12.gz Repository: wireless-nms-ftp ErrorCode: -618
2. Trying to upgrade with application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz wireless-nms-ftp
ncs/admin# application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz wireless-nms-ftp
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
6 [5964]: application:install cars_install.c[245] [admin]: Install initiated with bundle - PI-upgrade-bundle-1.2.1.12.tar.gz, repo - wireless-nms-ftp
6 [5964]: application:install cars_install.c[259] [admin]: Stage area - /storeddata/Installing/.1358123553
Stage 1 of 7: Transferring file ...
6 [5964]: application:install cars_install.c[263] [admin]: Getting bundle to local machine
6 [5964]: transfer: cars_xfer.c[54] [admin]: ftp copy in of PI-upgrade-bundle-1.2.1.12.tar.gz requested
7 [5964]: transfer: cars_xfer_util.c[92] [admin]: ftp get source - PI-upgrade-bundle-1.2.1.12.tar.gz
7 [5964]: transfer: cars_xfer_util.c[93] [admin]: ftp get destination - /storeddata/Installing/.1358123553/PI-upgrade-bundle-1.2.1.12.tar.gz
7 [5964]: transfer: cars_xfer_util.c[112] [admin]: initializing curl
7 [5964]: transfer: cars_xfer_util.c[125] [admin]: full url is ftp://132.234.254.29/PI-upgrade-bundle-1.2.1.12.tar.gz
-- complete.
6 [5964]: application:install cars_install.c[278] [admin]: Got bundle at - /storeddata/Installing/.1358123553/PI-upgrade-bundle-1.2.1.12.tar.gz
Stage 2 of 7: Unpacking file ...
6 [5964]: application:install cars_install.c[288] [admin]: Unbundling package PI-upgrade-bundle-1.2.1.12.tar.gz
-- complete.
6 [5964]: application:install cars_install.c[306] [admin]: Unbundling done. Verifying input parameters...
6 [5964]: application:install cars_install.c[328] [admin]: Manifest file is at - /storeddata/Installing/.1358123553/manifest.xml
6 [5964]: application:install cars_install.c[338] [admin]: Manifest file appname - NCS
7 [5964]: application:install cars_install.c[152] [admin]: UPGRADE: Comparing app version, installed: 1.1.2.12-1, new = 1.2.1.12-1
6 [5964]: application:install cars_install.c[401] [admin]: Manifest file pkgtype - CARS
6 [5964]: application:install cars_install.c[413] [admin]: Verify dependency list -
6 [5964]: application:install cars_install.c[425] [admin]: Verify app license -
6 [5964]: application:install cars_install.c[435] [admin]: Verify app RPM's
6 [5964]: application:install cars_install.c[443] [admin]: No of RPM's - 8
6 [5964]: application:install cars_install.c[454] [admin]: Disk - 50
6 [5964]: application:install ci_util.c[325] [admin]: Disk requested = 51200 KB
6 [5964]: application:install ci_util.c[345] [admin]: More disk found Free = 111955968, req_disk = 51200
6 [5964]: application:install cars_install.c[465] [admin]: Mem requested by app - 300
6 [5964]: application:install ci_util.c[369] [admin]: Mem requested = 307200
6 [5964]: application:install ci_util.c[384] [admin]: Found MemFree = MemFree: 4738352 kB
6 [5964]: application:install ci_util.c[390] [admin]: Found MemFree value = 4738352
6 [5964]: application:install ci_util.c[393] [admin]: Found Inactive = Inactive: 4208916 kB
6 [5964]: application:install ci_util.c[399] [admin]: Found Inactive MemFree value = 4208916
6 [5964]: application:install ci_util.c[409] [admin]: Sufficient mem found
6 [5964]: application:install ci_util.c[415] [admin]: Done checking memory...
6 [5964]: application:install cars_install.c[478] [admin]: Verifying preinstall zip...
6 [5964]: application:install cars_install.c[487] [admin]: Verifying RPM's...
3 [5964]: application:install ci_util.c[476] [admin]: Missing RPM (giflib-4.1.3-7.3.3.el5.x86_64.rpm) from bundle
3 [5964]: application:install cars_install.c[492] [admin]: App (NCS) has insufficient RPMs available in bundle
% One or more required RPM's not found in the bundle
6 [5964]: application:install install_cli.c[173] [admin]: error message: One or more required RPM's not found in the bundle
3 [5964]: application:install install_cli.c[177] [admin]: Error while Installing - Application bundle: PI-upgrade-bundle-1.2.1.12.tar.gz Repository: wireless-nms-ftp ErrorCode: -609
3. Trying to upgrade with application upgrade pi_1.2.1.12_update.tar.gz wireless-nms-ftp
ncs/admin# application upgrade pi_1.2.1.12_update.tar.gz wireless-nms-ftp
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
6 [6174]: application:install cars_install.c[245] [admin]: Install initiated with bundle - pi_1.2.1.12_update.tar.gz, repo - wireless-nms-ftp
6 [6174]: application:install cars_install.c[259] [admin]: Stage area - /storeddata/Installing/.1358125065
Stage 1 of 7: Transferring file ...
6 [6174]: application:install cars_install.c[263] [admin]: Getting bundle to local machine
6 [6174]: transfer: cars_xfer.c[54] [admin]: ftp copy in of pi_1.2.1.12_update.tar.gz requested
7 [6174]: transfer: cars_xfer_util.c[92] [admin]: ftp get source - pi_1.2.1.12_update.tar.gz
7 [6174]: transfer: cars_xfer_util.c[93] [admin]: ftp get destination - /storeddata/Installing/.1358125065/pi_1.2.1.12_update.tar.gz
7 [6174]: transfer: cars_xfer_util.c[112] [admin]: initializing curl
7 [6174]: transfer: cars_xfer_util.c[125] [admin]: full url is ftp://132.234.254.29/pi_1.2.1.12_update.tar.gz
-- complete.
Stage 2 of 7: Unpacking file ...
6 [6174]: application:install cars_install.c[278] [admin]: Got bundle at - /storeddata/Installing/.1358125065/pi_1.2.1.12_update.tar.gz
6 [6174]: application:install cars_install.c[288] [admin]: Unbundling package pi_1.2.1.12_update.tar.gz
-- complete.
6 [6174]: application:install cars_install.c[306] [admin]: Unbundling done. Verifying input parameters...
6 [6174]: application:install cars_install.c[328] [admin]: Manifest file is at - /storeddata/Installing/.1358125065/manifest.xml
6 [6174]: application:install cars_install.c[338] [admin]: Manifest file appname - NCS
7 [6174]: application:install cars_install.c[152] [admin]: UPGRADE: Comparing app version, installed: 1.1.2.12-1, new = 1.2.0.103-1
6 [6174]: application:install cars_install.c[401] [admin]: Manifest file pkgtype - CARS
6 [6174]: application:install cars_install.c[413] [admin]: Verify dependency list -
3 [6174]: application:install cars_install.c[417] [admin]: App (NCS) has insufficient dependencies CARS
% Failure occurred during request
6 [6174]: application:install install_cli.c[173] [admin]: error message: Failure occurred during request
3 [6174]: application:install install_cli.c[177] [admin]: Error while Installing - Application bundle: pi_1.2.1.12_update.tar.gz Repository: wireless-nms-ftp ErrorCode: -999
Any help is greatly appreciated.
Regards,
Sasha.

So the PI 1.3 is out now, finally! Though the upgrade from my current version of 1.1.2.12 is not supported...
"Upgrade from Cisco Prime Network Control System 1.1.2.12 or 1.1.3.2 to Cisco Prime Infrastructure 1.3.0.20 is not supported"
Anybody knows what to do now? Fresh install?

Similar Messages

Problem when upgrade NCS 1.1.1.24 to Prime 1.3.0.20

Dear Every one,
          I have problem with upgrading NCS 1.1.1.24 to Prine 1.3.0.20 The upgrade was stop on the step 3 of 7 as below;
     Stage 3 of 7: Executing pre-install ...
          % Pre-install step failed. Please check the logs for more details.
so I use command to show logging;
Apr 27 20:58:56 NCSSERV01 debugd[3104]: [11981]: application:install cars_install.c[550] [admin]: App (NCS) Preinstall script preinstall.sh failed; strings: '/opt/C
SCOncs/webnms/classes/com/cisco/wnbu/server/util/Version.class': No such file#012Patch existing , proceeding upgrade preinstall step:#012#0121.1.1.24#012Upgrade: /opt/
tempFolder4Upgrade already exists. Clearing it.#012Upgrade: Pre-install tempFolder4Upgrade creation Completed.#012#012Pre-install Safekeep Existing Version Started...#
012Pre-install Safekeep Existing Version Completed.#012#012Pre-install Safekeep Config Files Started...#012cp: cannot stat `/opt/CSCOncs/xmp_inventory/dar/customized-f
eature-parts/CONFIGURATION/*': No such file or directory#012Pre-install Safekeep Config Files Completed#012INFO: HA settings : /opt/CSCOncs/conf/rfm/classes/com/cisco/
common/ha/config/haSettings.xml#012INFO: Backing up HA settings...#012Starting Upgrade version checks...#012#012#0121.1.1.24#012ERROR: High Availability is enabled. Hi
gh Availability must be removed before attempting installation.#012
Apr 27 20:58:56 NCSSERV01 debugd[3104]: [11981]: application:install install_cli.c[173] [admin]: error message: Pre-install step failed. Please check the logs for m
ore details.
Apr 27 20:58:56 NCSSERV01 debugd[3104]: [11981]: application:install install_cli.c[177] [admin]: Error while Installing - Application bundle: PI-upgrade-bundle-1.2.
1.12.tar.gz Repository: defaultRepo ErrorCode: -635
Do you have any idea to resolved it?
Thank you for your response.

You will have to get back to the point where all NCS 1.1.1.24 processes are running----
1) ncs stop then ncs start
if that works then great:::: else
2) restore from working backup of NCS 1.1.1.24
Once you are there:::
1) remove HA
2) install patch 12
3) take backup
4) restore that backup to reformat the DB according to patch 12 executables
5) upgrade

Upgrade NCS 1.1.0.58 - Prime Infrastructure 1.3 or 1.2 - license

Hi!
I´m about to upgrade a customers appliance box to PI 1.3. Have anyone done it? and were there any issues with license?
I guessing an upgrade to 1.2 would be almost the same, license wise. If anyone has input fram that it would also be appreciated.
Any other input regarding the upgrade is also welcomed..
Regards
Fredrik

As I stated earlier the upgrade went fine but after about three days the database service stopped and wouldnt start again. It required a reinit of the db and then restore the db from backup to get it up again.
I had a TAC case on this and they gave me info about this in bug # CSCue88178.
CSCue88178 Inline upgrade from NCS 1.1.0.58 to 1.3 fails to update db schema
Symptom:
NCS 1.1.0.58 inline upgrade to 1.3 does not mention any errors during the upgrade process. However the db schema is never actually upgraded, and thus 1.3 does not start.
Conditions:
1. Installed ncs_patch-1.1.0.58-upgrade-12.tar.gz pre-patch.
2. Performed inline upgrade to NCS 1.3.0.20
Workaround:
Do not use inline upgrade; use restore upgrade instead.
This info was not available at the time of my upgrade.

Upgrade NCS 1.1.1.24 to Cisco Prime Infrastructure 1.2

Having a problem installing the ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz patch file on a virtual NCS before upgrading it to Cisco Prime Infrastructure 1.2.
I've followed the Cisco Prime Infrastructure 1.2 Quick Start Guide and did not had the same success as described in the document (see below):
gmsncs/admin# dir disk:defaultRepo/
Directory of disk:defaultRepo/
508376482 Sep 13 2012 05:38:25 backup-20120913-0530.tar.gpg
853768584 Sep 20 2012 05:40:17 backup-20120920-0530.tar.gpg
     127019 Sep 26 2012 16:40:58 ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz
           Usage for disk: filesystem
                 1544204288 bytes total used
                27185573888 bytes free
                30293413888 bytes available
gmsncs/admin# patch install disk:defaultRepo/ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Patch installation...
% Local file not found
Anybody experience with this procedure.
Thank You
--- Update ---
Skipped Step 4 and followed Step 5 in the Quick Start Quide, however now I receive a diffrent error:
gmsncs/admin# dir disk:/defaultRepo
Directory of disk:/defaultRepo
926193986 Sep 26 2012 17:48:12 GRDbackup-120926-1736.tar.gpg
508376482 Sep 13 2012 05:38:25 backup-20120913-0530.tar.gpg
853768584 Sep 20 2012 05:40:17 backup-20120920-0530.tar.gpg
     127019 Sep 26 2012 16:40:58 ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz
           Usage for disk: filesystem
                 2471309312 bytes total used
                26258468864 bytes free
                30293413888 bytes available
gmncs/admin# patch install GRDbackup-120926-1736.tar.gpg defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Patch installation...
% Manifest file not found in the bundle
gmsncs/admin#

Hi, Thank you again for your help, but I am still stuck. I have gathered the outputs from ncs start and a ncs status afterwards. Currently I am not able to access the web-UI of NCS..
deberncs01/admin# ncs startStarting Network Control System...This may take a few minutes...Dependency Check Failed: Matlab is not running.Dependency Check Failed: Ftp is not running.Dependency Check Failed: Tftp is not running.Failure during Network Control System startup. Check launchout.log for details.startdeberncs01/admin#deberncs01/admin#deberncs01/admin#deberncs01/admin#deberncs01/admin#deberncs01/admin# ncs statHealth Monitor is running, with an error.failed to start NCS on startup Health MonitorReporting Server is StartingFtp Server is FailureDatabase server is stoppedTftp Server is runningMatlab Server is runningNMS Server is stopped.SAM Daemon is not running ...DA Daemon is not running ...Syslog Daemon is not running ...statusdeberncs01/admin#
Anyone got a clue on that? and where can I find that launchout.log on NCS? Thank you

Upgrading NCS 1.1.1.24 to Prime 1.3 issues

I am currently running NCS 1.1.1.24 and trying to upgrade to prime 1.3, but running into some issues, i applied the patch ncs_patch-1.1.1.24-upgrade-12.tar.gz, but when i try to acutally upgrade i get the following...
admin# application upgrade PI-upgrade-bundle-1.3.0.20.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
% One or more required RPM's not found in the bundle
I have even tried to just upgrade to 1.2 but that doesnt work as well...
admin# application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
% One or more required RPM's not found in the bundle
I have verifed the patch was install correctly...
admin# patch install ncs_patch-1.1.1.24-upgrade-12.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Patch installation...
% Patch is already installed.
Any help would be appreciated, Thanks.
-Bryan

Figured out the issue, somehow both upgrade files were corrupt, once i verified the checksum, i realized that. The upgrade is working now.

Upgrade NCS 1.1.1.24 to CPI 2.1.0.0.87

Hi, guys.
I have upgraded our NCS 1.1.1 installation to Cisco prime Infrastructure 2.1.0.0 by taking a backup of NCS 1.1 and restoring the backup to a clean installation of CPI 2.1 (exactly as is stated in the Cisco documentation).
Basically this process has worked ok (all devices, maps, etc. have been imported into CPI 2.1), but it turns out, that some of the NCS licenses have not been imported into CPI 2.1, see attached screenshots:
The red-marked lic file (ending on 8212) is missing on CPI 2.1, it is an AddOn license for 300 access point.
All other AddOn access point licenses have been successfully imported, also the MSE licenses.
Is this supposed to happen ???? What can be the reason why it hasn't been imported ???

Hi Frank,
As per the description provided , looks like everything was restored fine except that license file.
Ideally with the restore all the license , should also be restored.
it would be difficult to tell you why it happened , however ,if you have the copy of license just go ahead and
apply it or if you don't have the license copy then contact the LICENSE team to re-issue the license.
***If someone has a different view about the issue , share with us****
Thanks-
Afroz
***Ratings Encourages Contributors ****

Upgrade WCS 7.0 to PI 1.2 via NCS 1.1

Hello all,
we have started to do the upgrade from WCS 7.0 to PI12. In order to do that we first need to upgrade to NCS 1.1. We have ordered the following from Cisco:
R-W-PI12-M-K9
WCS 7.0 to Cisco Prime   Infrastructure 1.2 Migration
N/A
14 days
No
N/A
1
1.995,00
1.995,00
0
1.995,00
R-PI12-BASE-K9
Prime Infrastructure 1.2 Base   License and Software
N/A
14 days
Yes
N/A
1
0,00
0,00
0
0,00
L-PI12-LF-500-LIC
Prime Infrastructure 1.2 -   Lifecycle - 500 Device Lic PAK
N/A
14 days
Yes
N/A
1
0,00
0,00
0
0,00
L-PILMS42-500-M
Prime Infrastructure LMS 4.2 -   500 Device Upgrade Lic
N/A
14 days
Yes
N/A
1
0,00
0,00
0
0,00
L-PI12-LF-100-LIC
Prime Infrastructure 1.2 -   Lifecycle - 100 Device Lic PAK
N/A
14 days
Yes
N/A
3
0,00
0,00
0
0,00
L-PILMS42-100-M
Prime Infrastructure LMS 4.2 -   100 Device Upgrade Lic
N/A
14 days
Yes
N/A
3
0,00
0,00
0
0,00
L-W-PI12-500-M
WCS to Prime Infrastructure 1.2   Migration 500 Device
N/A
14 days
No
N/A
1
0,00
0,00
0
0,00
L-W-PI12-100-M
WCS to Prime Infrastructure 1.2   Migration 100 Device
N/A
14 days
No
N/A
3
0,00
0,00
0
0,00
I have done the upload of the XML File from our WCS 7.0 installation to get the License File. But on the NCS 1.1 installation the following License is needed first (Cisco Prime Network Control System 1.1 Config Guide):
NoteBefore adding the licenses that are migrated from your WCS installation, apply the L-WCS-NCS1-M-K9 license. The licenses migrated from WCS are generated as “ADD” licenses, and you cannot apply them unless you apply the L-WCS-NCS1-M-K9 license.
L-WCS-NCS1-M-K9 is the Product Number to do the upgrade from WCS 7.0 to NCS 1.0, R-WCS-PI11-M-K9 is the product number to dothe upgrade from WCS 7.0 to NCS/PI 1.1.
If I try to install just the License File I get from Cisco using the XML file from our WCS 7.0 installation, I get the error "Unable to add any license without an NCS (L-NCS-1.0-K9) license.".
But how do a get this license if I ordered R-W-PI12-M-K9 (WCS 7.0 to PI1.2 Upgrade License)? What is the step to get the right License?
Many thanks in advance for any help on that issue.
Best regards,
Hans

Hello Joe,
no. The information in the deployment Guide (the link i proveded before) is wrong.
You still need to follow the upgrade path WCS 7.0 -> NCS 1.1 (here you have to use for example 1.1.1.24, because 1.1.2.12 cannot be upgraded to PI 1.2), then you can upgrade NCS 1.1 to PI 1.2 (if you upgraded the WCS to NCS 1.1.1.24 you need to install a patch ncs_patch-1.1.1.24-upgrade-12.gz, for other 1.1 releases you need a different patch).
The major problem was the licensing. Because with the order of the Upgrade Licenses from WCS 7.0 to PI 1.2 I got "normal licenses", for PI 1.2, a Base License and Lifecycle Licenses (the number of Lifecycle Licenses matches the number from the order).
Because we ordered the WCS 7.0 to PI 1.2 Upgrade Licenses I also ordered the NCS Appliance with the PI 1.2 (before I thought a direct upgrade from WCS 7.0 to PI 1.2 should be possibel, why not, if you can order the licenses with the description Upgrade License WCS 7.0 to PI 1.2 :-)). So I had to downgrade the NCS Appliance to NCS 1.1. After the downgrade the NCS Appliance came up without any licenses. So the major porblem was that I could not use the PI 1.2 licenses (they are not installable on NCS 1.1). So I got a demo/temporary license from Cisco for NCS 1.1 to do just the migration. After the final upgrade to PI 1.2 I installed the base and the lifecycle licenses and now everything is fine.
Best regards,
Hans

Upgrading Cisco NCS 1.1.1.24 to Prime Infrastructure 1.2

I am planning to upgrade NCS 1.1.1.24 to Prime Infrastructure 1.2 and want to make sure that I understand the process and what to expect. Any input from those of you that have completed this would be very appreciated. I am planning on doing the inline upgrade.
I plan to follow the guide and first install the point patch. ncs_patch-1.1.1.24-upgrade-12.tar.gz
Then the upgrade image file is PI-upgrade-bundle-1.2.1.12.tar.gz.
What I want to make sure is that I do not lose any data or maps. Is this retained?
We use the NCS Guest Portal for Guest wireless ID administration. Is this the same in Prime 1.2?
Thanks.

The portal guest administration is the same might look different.
The process is just like you mentioned. Install the patch and then perform the upgrade. When you go to Prime Infrastructure, don't be nervous if it takes PI 10 minutes to boot. That's normal... From the CLI, you can issue a show application status ncs. NCS is case sensitive!
Sent from Cisco Technical Support iPhone App

NCS appliance upgrade 1.1.1.24 - 1.3

Tyring to upgrade NCS as below and it fails with the error "% One or more required RPM's not found in the bundle"
/admin# application upgrade PI-upgrade-bundle-1.3.0.20.tar.gz FTP
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
% One or more required RPM's not found in the bundle
Version information of installed applications
Cisco Prime Network Control System
Version : 1.1.1.24
Any help would be appreciated
Brendan

kindly check the following link for the reference (Prime upgrade)
https://supportforums.cisco.com/docs/DOC-36703
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/2.0/release/notes/cpi_rn.pdf

Upgrade Prime NCS

I have a Prime NCS appliance running 1.0.2.29 and I need to upgrade it to 1.1.0.58. I have downloaded the code from the Cisco site but I need to know how to upgrade the NCS.

Use the following command to upgrade from NCS 1.0 to NCS 1.1.0.58:
# application upgrade NCS-upgrade-bundle-1.1.0.58.tar.gz wcs-ftp-repo
In the preceding command, NCS-upgrade-bundle-1.1.0.58.tar.gz is the upgrade bundle file, which is available for download.
The repository used in the example, wcs-ftp-repo, can be any valid repository.
Examples of repository configurations follow.
FTP Repository:
# configure
(config)# repository wcs-ftp-repo
(config-Repository)# url ftp://ip-address
(config-Repository)# user ftp-user password plain ftp-user
(config-Repository)# exit
(config)# exit
SFTP Repository:
# configure
(config)# repository wcs-sftp-repo
(config-Repository)# url sftp://ip-address
(config-Repository)# user ftp-user password plain ftp-user
(config-Repository)# exit
(config)# exit
TFTP Repository:
# configure
(config)# repository wcs-tftp-repo
(config-Repository)# url tftp://ip-address
(config-Repository)# exit
(config)# exit
#

Cisco NCS Prime upgrade error : "% Manifest file not found in the bundle"

Hello ,
I am currently trying to upgrade my NCS software from 1.0.1.4 to 1.1.1.24 using the upgrade bundle .
Running the upgrade procedure i receive the following error message :
|---------------------------------------------------------------------------------------------------------------------------|
CPNCSSRV/admin# application upgrade NCS-upgrade-bundle-1.1.1.24.tar.gz ncs-ftp-repo
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
% Manifest file not found in the bundle
|---------------------------------------------------------------------------------------------------------------------------|
Just to make it clear :
1. the .tar file isn't corrupted
2. there are no typo's
3. the repository is fine
Any ideas would be appriciated .
Thanks ,

Hi,
In case anyone encountered the same problem, here is how you solve it:
1- Login into shell by typing "shell command" from NCS enable mode.
2- Copy the installation zip file to local disk directory:
        cp /source-path/name/installation-file-name.zip /localdisk
3- Browse to localdisk directory which exists in the root directory and unzip the zip installation file:
          [LMS/root-ade localdisk]# unzip installation-file-name.zip
4- Exit shell by typing "Exit"
5- At this step, if you type the "dir" command, the installation file "NCS-upgrade-bundle-1.1.1.24.tar.gz" should appear.
6- In "conf t" mode, create a new repository
   repository myrepo
          url disk:/
7- application upgrade NCS-upgrade-bundle-1.1.1.24.tar.gz myrepo
Please rate if you find helpful.
Thanks.
Moath Rawashdeh

Upgrading Wireless Infra.

Hi Experts,
I am planning to upgarde current Cisco 5508s and Cisco WCS. We have currently 1142n APs (around 400) and we will be adding 3600 APs to existing network.
I am planning to move from current code to the latest code and I would like to know any considerations or if anyone has done similar upgrades and can share their experience, any bugs or issues encountered.
WLCs 5508 upgrade from 6.0.182.0 (current) to 7.0.220.0 (Intermediate) and the to 7.4.100.60 (Final) with FUS upgrade from 1.3 to 1.7
WCS to Prime Infra 1.2 : WCS 6.0.132.0 (current VM) to 7.0.220.0 then install new NCS 1.1.1.24 (VM) and migrate WCS data to NCS 1.1.1.24 and finally upgrade NCS 1.1.1.24 to Prime Infra 1.2.1.12 (VM) and decommision WCS. I will apply license after upgrade to Prime Infra. (WCS to Prime migration license).
Please share your thoughts.
Thanks in advance.
hardik..

All sound good, If you want to prepare for down the road technology (if is a big structure) you should think that for every 3 ap keep one as 1142, and two of 3600 then in the future you could add the 802.11ac module and the next Wi-Fi/Micro Cell DAS module for 3600 (Still on the works) that should be available Oct-Dec time frame... By using 7.4 or higher on WLC & MSE with Prime 1.3 or higher you will add some other capabilities to your network (Cisco Connected Mobility Experience CME-CMX http://www.cisco.com/en/US/netsol/ns1205/index.html )
If you have any question, comments or concern please contact me...
Thank you,
Manuel Baez
Sales Eng
Need help ? call Sales Acceleration Center(SAC) at Toll Free (USA) :1-800-225-0905 International +1-408-902-4872 or send email to [email protected] or Live Chat: http://tinyurl.com/sacucs

NCS failing to gather current clients from APs

We're running NCS 1.1.0.58. Since updating to this release from the 1.0 release, the 'Autonomous AP Client Status' and 'Lightweight Client Status' background tasks have been failing with message 'java.lang.NullPointerException'. I believe as a result of this that the 'Current Clients' tab on an AP monitoring screen just reports 'No data available'.
Does anyone have any suggestions of how to fix this?
Thanks,
Sean

Hi;
We had the same problem, running NCS 1.1.0.58. I saw that 1.1.1.24 was out, so I downloaded the NCS-upgrade-bundle-1.1.1.24.tar.gz and applied it. Seems to have fixed the problem, no need for the horror of opening a TAC case.
Instructions here:
http://www.cisco.com/en/US/docs/wireless/ncs/1.1/release/notes/NCS_RN1.1.1.html#wp208350
Pertinint section below.
Steve
Shut down NCS before performing the upgrade. To stop NCS, enter the ncs stop command.
Use the following command to upgrade from NCS 1.0 to NCS 1.1.1.24:
# application upgrade NCS-upgrade-bundle-1.1.1.24.tar.gz ncs-ftp-repo
In the preceding command, NCS-upgrade-bundle-1.1.1.24.tar.gz is the upgrade bundle file, which is available for download.
The repository used in the example, ncs-ftp-repo, can be any valid repository.
Examples of repository configurations follow.
FTP Repository:
# configure
(config)# repository ncs-ftp-repo
(config-Repository)# url ftp://ip-address
(config-Repository)# user ftp-user password plain ftp-user
(config-Repository)# exit
(config)# exit
SFTP Repository:
# configure
(config)# repository ncs-sftp-repo
(config-Repository)# url sftp://ip-address
(config-Repository)# user ftp-user password plain ftp-user
(config-Repository)# exit
(config)# exit
TFTP Repository:
# configure
(config)# repository ncs-tftp-repo
(config-Repository)# url tftp://ip-address
(config-Repository)# exit
(config)# exit

WCS 7.0 to CPI 1.2 Migration?

I bought the following product:
1
WCS 7.0 to   Cisco Prime Infrastructure 1.2 Migration
R-W-PI12-M-K9
1
2
Prime Infrastructure   1.2 Base License and Software
R-PI12-BASE-K9
1
3
Prime Infrastructure   1.2 - Lifecycle - 1K Device Lic PAK
L-PI12-LF-1K-LIC
2
4
Prime Infrastructure   LMS 4.2 - 1K Device Upgrade Lic
L-PILMS42-1K-M
2
5
WCS to Prime   Infrastructure 1.2 Migration 1K Device
L-W-PI12-1K-M
2
And got Product Auhorizationg Keys.
I have a next question:
1) I need to activate and set L-PILMS42-1K-M or enough to activate and set R-PI12-BASE-K9 and L-PI12-LF-1K-LIC?
2) I can install Cisco Prime Infrastructure 2.0 and set R-PI12-BASE-K9 and L-PI12-LF-1K-LIC or need to install CPI 1.3 and then update to CPI 2.0?
Please help me with this problem.

You'll need to activate
R-W-PI12-M-K9,
R-PI12-BASE-K9,
L-PI12-LF-1K-LIC,
L-W-PI12-1K-M
but not
L-PILMS42-1K-M
In order to get to 2.0 from WCS 7.0::
You'll need to migrate your data from WCS to NCS as shown in the link below
https://supportforums.cisco.com/docs/DOC-26973
Then upgrade NCS to Prime 2.0
Or
You can simply export your maps from WCS then import them into a newly built Prime 2.0 server once you've added the controllers.
The 2nd option is a whole lot easier and a whole lot faster but any customization you've done in WCS like special reports, added users to access the browser and other mods like TACACs settings as well as performance datawon't come over but if you're intested in just getting the maps and AP placement, go this route

Cisco Prime Infrastructure 1.2 licensing

I have a customer that is running CiscoWorks 3.2 and they also have NCS 1.1 (upgraded from WCS 7.0). They have found that it costs way more to upgrade CiscoWorks to Cisco Prime Infrastructure than it would be to just buy licenses after they finish upgrading NCS to Cisco Prime 1.2.
The main question about Cisco Prime 1.2 is how the licensing works, we need to know if the licensing will work the same as it did for CiscoWorks where they only needed one license for a full stack of switches. They believe that Prime 1.2 will require a license for each switch in the stack, which will cause them to buy several more licenses than what they feel they can afford.
If anyone knows how the licensing works, it would be appreciated.
Thanks.

Have you gone through the below link
http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/prime-infrastructure/guide_c07-714720.html

Upgrading NCS 1.1.1.24 to PI 1.2.1

Similar Messages

Maybe you are looking for