NCS upgrade to 1.2

We are getting ready to upgrade our NCS 1.1.0.58 to PI 1.2. There is a patch that needs installed on NCS before we can upgrade. Can I patch the system now before we do the full upgrade and keep everything running normal for a few weeks? Also we have a WCS still running that we are trying to move controllers over to NCS. We want to convert the licenses to NCS. I know I can convert My WCS 7.0.172 licenses to NCS 1.1,0.58 but if I have to upgrade my NCS before I can convert the licenses, can I convert the WCS licenses to NCS 1.2 licenses?
Sent from Cisco Technical Support iPhone App

Yes you can patch whenever. As far as license, you can do the license once you have the NCS up to get the udi and the serial of the VM. By the way, your WCS needs to be at 7.0.220.0 or later to export the WCS data. The doc is wrong!
Sent from Cisco Technical Support iPhone App

Similar Messages

NCS Upgrade Version 1.1.0.58 - Problems ?

Hello,
I need to Upgrade my NCS to version 1.1.0.58. Actually my NCS is in the version 1.0.1.4 and i have a lot of templates configured and 1500 Access Points applied.
I have 5 WLCs and will do too the upgrade in the WLCs to version 7.2.130.0.
Will I lose some configuration with these upgrades ? Because the version 1.1.0.58 has more features than version 1.0.1.4 in the NCS and the WLC was adjusted some bugs.
The configurations that i has in the NCS version 1.0.1.4 is H-REAP and in the version 1.1.0.58 will be the FlexConnect, theoretically is the same, but i don't know if the configuration is the same in the two versions.
Will i have some problem with these upgrades ?
Can i do a downgrade in the NCS from version 1.1.0.58 to 1.0.1.4 if i have problems ? I was looking for a document who show how can i do this, but i didn't find nothing about.
Thanks.

Upgrade an downgrading is very much the same. When you upgrade, you shouldn't loose anything, if you downgrade you might, depending if you have a feature in the newer version that isn't supported in the older version. Take a look at the release notes for specifics on upgrading to the 1.1.058 version, they will have everything in there for you to perform the upgrade.
http://www.cisco.com/en/US/docs/wireless/ncs/1.1/release/notes/NCS_RN1.1.html#wp208350

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?

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

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

NCS 1.1 with license that are 1.0

I have installed the 1.1 OVA but when i try to upload the 1.0 license and get an error. Is the error dude to the fact the version is 1.1 and I'm trying to upload 1.0 licenses?
thanks in advance..
izzy

Islam,
Licensing is tied to the (V)UDI of the NCS. If you have 1.0, you should upgrade to 1.1 using the NCS-upgrade package, not install 1.1 fresh with a new OVA.
If you are already on a new 1.1 OVA and you don't have your old 1.0 install anymore, then you will need to have Cisco Licensing regenerate your license file.
Regenerations are limited on NCS to, I think, 2 or 3, so don't do this too often.
Detailed upgrade instructions and explanations of UDI and VUDI are in the 1.1 release notes.
Justin
Sent from Cisco Technical Support iPhone App

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

[SOLVED] Upgrade from SLES10 SP3 & OES2 SP2 to SP4/SP3 breaks NCS

Hi folks,
(This post was originally meant to be a rant and a request for help, but
while writing the final paragraph i found the solution. It's still a
rant, but i figured i'd post my solution here in case someone else runs
into the same issue.)
I've just spent several hours banging my head against a broken cluster
node. My system is a 32-bit SLES 10 VM running on VMware ESX 3.5.x.
I upgraded from SLES10 SP3 and OES2 SP2 to the next service packs for
each (using the move-to-oes-sp3 script in yast2 online_update).
Everything went well for the first few update/reboot sequences, then
after the final reboot on SLES10 SP4 & OES2 SP3, cluster services would
not load or join the cluster on restart.
I checked dmesg and found errors about "Loading module compiled for
kernel version 2.6.16.60-0.54.5-vmi" into a previous kernel version, so
i tried downgrading to that kernel version, only to find that it was
older than the one i had just upgraded from (it's the original SLES10
SP3 kernel). So i tried upgrading back to the same kernel which is
running on the other cluster node (2.6.16.60-0.77.1-vmi), but that did
not work any better.
<preaching>
I have to say that i'm not impressed that OES2 SP3 isn't even compiled
against the appropriate kernel, and because of SUSE's kernel RPM
overwrite policy there's no way i can select to boot from a previous
kernel to see if that fixes things. Note to SUSE and other distro
builders: if you're not doing kernel package upgrades like Red Hat or
Ubuntu (so that we can select to boot from the previous kernel from the
boot menu), you're doing it *WRONG*.
</preaching>
I then upgraded again to the latest recommended kernel for SLES10 SP4,
and still no joy. Dmesg shows this error before the rot starts:
allocation failed: out of vmalloc space - use vmalloc=<size> to increase
size.
When searching for this error i stumbled across
http://ubuntuforums.org/showthread.php?t=1613132
which pointed me to
http://www.mythtv.org/wiki/Common_Pr...lloc_too_small
Adding vmalloc=192M to /boot/grub/menu.lst and rebooting solved the
problem for me.
Regards,
Paul

Originally Posted by Paul Gear
On 13/10/11 07:36, magic31 wrote:
> ...
> Not sure if it's related to the issue you've hit, but along the lines
> of what Kevin already mentioned, there are issues that can arries when
> using the VMI kernel (that I've seen) if having multiple flavors of the
> kernel installed along with it (as in having both kernel-vmi as also
> kernel-smp packages installed) ...
> Curious, is that also the case with your setup?
The system in question has kernel-bigsmp and kernel-vmi installed. We
only ever boot from kernel-vmi.
> I've moved to only using the smp kernel on VMware (along with the
> clock=pit boot option to avoid time drift issues, or pmtr I think in
> your case when also running NCS services in the vm).
When we installed the system (on OES2 SP1, i believe) it was a while
ago, and kernel-vmi with clocksource=acpi_pm on the kernel command line
was the only solution we could find to get reliable time. If there are
updated best-practice documents, i'd be happy to hear about them.
However, this is a production cluster and my boss is (rightly) rather
reticent to make major changes.
Paul
the official Vmware paper on time is that IF you're using SLES 10.x 32-bit you will use VMI and NO kernel params (ie, get rid of the clockpit and clocksource=blah).
But if 64-bit then you're okay.
The easiest, IMO (especially with vmware) is to use the miggui (migration utility). That's how I'm converting all my 32-bit servers in vmware to 64-bit. Works quite well.
--Kevin

Problem after upgrade a PRIME-NCS-APL-K9 from version 1.1.0.58 to Prime Infrastructure 1.2

I have upgraded a PRIME-NCS-APL-K9 from version 1.1.0.58 to Prime Infrastructure 1.2
First I have installed the Path "ncs_patch-1.1.0.58-upgrade-pi_1.2.tar.gz" and then the
"PI-upgrade-bundle-1.2.0.103.tar.gz".
after the upgade I have got the Message "Upgrade Successful".
Now when I start the NCS i get the following error message
egghead/admin# ncs start
Starting Network Control System...
Unable to verify hardware.
This may take a few minutes...
Health Monitor is already running.
Failure during Network Control System startup. Check launchout.log for details.
In the launchout.log are this messages:
Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
truststore used is /opt/CSCOlumos/conf/truststore
truststore used is /opt/CSCOlumos/conf/truststore
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
Starting Remoting Service: Reporting Server
Checking for running servers.
00:00 Check complete. No servers running.
Starting Server ...
Starting Remoting Service: Reporting Server
The Report Server startup script is already running waiting for report server to start
Starting Remoting Service: Reporting Server
The Report Server startup script is already running waiting for report server to start
Starting Remoting Service: Reporting Server
The Report Server startup script is already running waiting for report server to start
Starting Remoting Service: Reporting Server
The Report Server startup script is already running waiting for report server to start
have anyone an idea whats wrong?
thank you for your help
Kurt

i have the same problem
NCS/admin# ncs status
Health Monitor Server is starting.
Reporting Server is Starting
Ftp Server is running
Database server is running
Tftp Server is running
Matlab Server is running
NMS Server is stopped.
SAM Daemon is running ...
DA Daemon is running ...
Syslog Daemon is running ...
status
I try it
To get it back up and running do the following from the CLI.
1. Stop the NCS
2. Run 'ncs db reinitdb'
3. Start the NCS
but the status is the same

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

LMS 4.1 (Windows) & NCS 1.1 (VM) Upgrade to Cisco Prime Infrastructure 1.2

Hi All,
Im getting a bit confused about the whole upgrade migration process for the following config to Cisco Prime Infrastructure:
LMS - Version 4.1 , 500 devices. Windows Server 2008 R2 Standard SP1
NCS – version 1.1 , 50 devices Red Hat Linux ( 64 Bit) (Installation software - NCS-VA-1.0.1.4-small.ova)
I want to be able to backup databases and migrate licensing from LMS and NCS to one platform. Does anyone have experience of this and could possible guide me thorugh this process. LMS has SAS and NCS has SAU.
Help will be very much appreciated!!

It's a couple of steps but can be done. You may want to reconsider getting off of LMS since the latest Prime Infrastructure (PI 1.2) does not have full feature compatibility with the latest LMS (4.2.3). Have a look here for the comparison.
If you still want to do it:
1. Upgrade your NCS to PI 1.2 (instructions). If you're going with a total of 550 devices on a combined license you should use the medium ova file to get the correct server resource allocation. You will need to get the new license from the TAC or via the licensing portal. I'm not sure if you can get the PI license for your LMS upgrade directly via the portal but you do have the entitlement for LMS 4.2 and PI 1.2 (combined licenses not to exceed the original LMS number) if your SAS is current. You may need to contact the TAC and ask for the licensing team.
2. Upgrade your LMS to 4.2 and patch it to 4.2.2 (instructions). Once you've done that, there is a simple menu command to export your device credentials to Prime (Admin, System, Export Data to PI in LMS and then Operation, Device Work Center, Bulk Import in PI - instruction on Page 18 here). Do that and then in the new PI installation import the devices.
Verify everything is working and you can decommission the LMS server.

NCS to PI 1.2 upgrade question

Hello
I have PRIME-NCS-APL-K9 (appliance not VM). Current version is 1.1.0.58 and I need to upgrade to Prime Infrastructure 1.2
Is it possible to do this with the same HW? I have heard that the HD are to small and they have to be replaced by Cisco?
Do anyone have some information or experience about that?
regards
Darek

Cisco used to ship the appliance with just under a half Terabyte of Drive Space which could be a problem for larger installs.
For smaller installs it shouldn't be a problem. You just won't be able to add more disk space if needed.
If the device has HW maintenance and has the smaller drive config, it could be RMAd...

NCS upgrade to 1.2

Similar Messages

Maybe you are looking for