topic Upgrade from NCS to Prime in Wireless

Upgrade from NCS to Prime

Johan Lindstrand — Sun, 04 Jul 2021 05:48:37 GMT

Hi.

I am trying to upgrade from NCS ver 1.1.1.24 to Prime 1.2. With the script ncs_patch-1.1.1.24-upgrade-pi_1.2.tar.gz.

And everything runs smooth until Stage 6 of 7., when Updating Database Schema .. is starting

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 ...

-- complete. Time Taken : 0 hr, 0 min, 52 sec

Stage 2 of 5: Schema Upgrade ...

: This could take long time based on the existing data size.

Here everything stops. I have waited for 5 hours now is this normal?

Regards

Johan

Upgrade from NCS to Prime

wimatwork — Thu, 11 Oct 2012 13:28:19 GMT

Depends on your database size, for me the whole upgrade took 5 hours.

Upgrade from NCS to Prime

raun.williams — Thu, 11 Oct 2012 14:21:44 GMT

How big is your deployment? Like wim, this took me forever. Then again, alot of things in NCS/PI can take forever.

Upgrade from NCS to Prime

Johan Lindstrand — Thu, 11 Oct 2012 18:00:48 GMT

My deployment is 4st WISM2 controllers and 4st WISM controllers. It’s about 1500 st AP so it’s quit large deployment.

Finally after 7 hours is was OK. But this was not end of my problems. The login page appears OK, but I can’t use IE9 to access this web. (the page can’t be display). Had to use (Chrome) to login.

But when I had logged in all my Licenses and all my Maps where erased !!

Is it possible to restore Licenses + Maps from my old NCS database ???

Upgrade from NCS to Prime

Peter Nugent — Sat, 13 Oct 2012 01:56:31 GMT

It looks like you may be able to restore the data as it says here but you may need to simply export the database, install PI and restore.

http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/quickstart/guide/cpi_qsg.html#wp56790

Upgrading Cisco Prime Infrastructure

You can upgrade the following Cisco Prime Network Control System products to Cisco Prime Infrastructure 1.2:

•Cisco Prime Network Control System 1.0.0 (NCS 1.0 MR2, 1.0.2.29)

•Cisco Prime Network Control System 1.1.0 (NCS 1.1 FCS, 1.1.0.58)

•Cisco Prime Network Control System 1.1.1 (NCS 1.1 K MR1, 1.1.1.24)

•Cisco Prime Network Control System (WAN) 1.1.0 and Cisco Prime Assurance Manager 1.1.0 (NCS-WAN/PA 1.1 FCS, 1.1.0.1114)

•Cisco Prime Network Control System (WAN) 1.1.1 and Cisco Prime Assurance Manager 1.1.1 (NCS-WAN/PA 1.1.1 MR1 FCS, 1.1.0.1116)

You can upgrade using either of the following methods:

1. Standard—Upgrades your existing system to version 1.2. All existing data is retained and you will be using the same size OVA at the end. The existing product will not be operational until the upgrade is complete. This is the normal option for most users. For details, see Performing a Standard Upgrade.

2. Migration—Allows you to back up the data from your existing system, install Cisco Prime Infrastructure 1.2 as a new system, and restore the existing system's data to the new system. You can then decommission the old system. This option is preferred if you want to migrate to a larger OVA, cannot disturb your production system, or have a large network. For details, see Performing a Migration Upgrade.

Re: Upgrade from NCS to Prime

Scott Fella — Sat, 13 Oct 2012 13:54:28 GMT

I had a WCS to NCS in which the export took over 8 hours and the export zip file was around 16gb. So now when I have any WCS to NCS migrations, I usually run the export in the evening and then the import the next morning. The following day I finalize the NCS install.

Sent from Cisco Technical Support iPhone App

Upgrade from NCS to Prime

jlinkowsky — Sun, 14 Oct 2012 21:45:03 GMT

I attempted the restore from 1.1.1.24 to prime 1.2 clean OVA install. The restore literally took over 40 hours. However when it completed all the services wouldn't start. Nms and health monitor failed. Talked to TAC and turns out there is a bug when restoring 1.1.1.24 data to 1.2. The engineer told me that he has had many customers have the same issue.

My advice is stay in your current version until 1.2.x is out and vetted. I have lost 3 days trying to get this to work. Looks like it won't until 1.2 is fixed.

I am now trying to get 1.1.1.24 back and working. Not easy either.

Just my $.02

John L.

Upgrade from NCS to Prime

Peter Nugent — Mon, 15 Oct 2012 00:07:45 GMT

Could you supply details of the bug that you are up against?

Upgrade from NCS to Prime

jlinkowsky — Mon, 15 Oct 2012 00:32:07 GMT

Sure. I was provided this Bug ID from Level 1 Cisco TAC today:

CSCuc29378 Prime Infrastructure 1.2 won't start after a db restore from NCS1.1.1.24

Also, funny enough, I have been trying to restore my 1.1.1.24 to a NCS 1.1.1.24 install (since Prime 1.2 isn't working), and guess what? There is an Oracle bug for THAT restore as well:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtw59460

Bottom line for me is, I have to start from scratch with either 1.2 or 1.1.1.24 - I will lose all of my historical data.

John L.

Upgrade from NCS to Prime

xevit_service — Wed, 17 Jul 2013 08:17:27 GMT

Im hitting the same problem! But with version 1.3.

I migrate the customer WCS to NCS 1.1.1.24. Then i want to upgrade to version 1.3.0.20. I installed the appropiate patch and upgrade to 1.3. After the upgrade process it is not possible to start the NCS Service completely. The NMS Service and the Health Monitor wont start!

Is there anybody else who has the same problems?

Upgrade from NCS to Prime

Rob Johnson — Thu, 18 Jul 2013 04:38:46 GMT

The upgrade patch needs to be installed on the 1.1.1.24 box prior to running the ncs migrate command.

1) install ncs 1.1.1.24

2) install patch (ncs_1_1_1_24-Update.13.4.tar.gz or update patch 12)

3) run ncs migrate

4) upgrade to 1.3.0.20

start ncs

NCS will start when it's done in this order

BTW:: be sure to run the restore from a console session so the ssh session doesn't time out

Upgrade from NCS to Prime

senthilkumar.meenakshisundaram — Fri, 26 Jul 2013 22:47:58 GMT

Hi ,

Have you resolved this issue ? I am facing the same issue mentioned by you ( NCS 1.1.1.24 to PI 1.3).

Please shed some light .

Thanks,

Senthil

Upgrade from NCS to Prime

MATS KARLSSON — Tue, 20 Aug 2013 06:05:56 GMT

I now experience similar problems.

I right now trying to upgrade from NCS ver 1.1.1.24 to a new Prime 1.3 clean OVA installation.

I attempted the restore database from 1.1.1.24 to prime 1.3 clean OVA install.

I the first attempt the database restore corrupted the applications so and was never possible to start again.

I needed to redo the OVA installation.

Now I´m in on my second try to resore with a new dackup file but ssh session timesout after about 6 hours and

I do not have a clue if it still doing some restore work or not.

Do any one know how to verify if there is activity ongoing with restore ??

("show restore history" is empty)

I afraid that I might use the “ncs start” to early and corrupt the restore process.

/mats

Upgrade from NCS to Prime

Rob Johnson — Tue, 20 Aug 2013 09:59:38 GMT

Please run the restore from a console port to keep the session from timing out.

Upgrade from NCS to Prime

MATS KARLSSON — Tue, 20 Aug 2013 11:13:27 GMT

Thanks !

But do you mean I should type in my hole starting command one again ?

In my case:

"restore ncsprod-130812-0944.tar.gpg repos mlan-ftp-repo application NCS"

Does it not then, start all over again, from the beginning ??

Upgrade from NCS to Prime

Rob Johnson — Tue, 20 Aug 2013 11:16:03 GMT

What I would do is::

1) ncs db reinitdb

2) rerun the entire restore command again from a console port

why? who knows what shape the DB is in since the restore session timed out part way through the process:::

Upgrade from NCS to Prime

MATS KARLSSON — Tue, 20 Aug 2013 11:42:36 GMT

Ok !

Yes, my SSH session timed out, but I do not know for sure that the restore process has stoped.

I hesitate to start it all over again if i do not know if it has halted or stopped.

I have a huge database ( 24 GiB)

I now have an open TAC-case on this one. The the advice is to stay calm as the logs claims it still doing something.

I would like to that the "ncs status" shows that the database server i stopped, now it is in state "running".

I would like it to be an idicator of a process goin on or not.

#ncs status

Health Monitor is stopped.

Reporting Server is Stopped

Ftp Server is Stopped

Database server is running

- - -

Re: Upgrade from NCS to Prime

Scott Fella — Tue, 20 Aug 2013 11:56:59 GMT

It seems like the first three services failed to start or else it would show initiating or something like that. You can do an NSC stop and NSC start and see if you see any errors.

Sent from Cisco Technical Support iPhone App

Upgrade from NCS to Prime

MATS KARLSSON — Tue, 20 Aug 2013 12:09:36 GMT

It has not failed. It is stop and should be so.

All the services has been stopped to do the restore. Nothing was running before I started restore and i have not

restarted anything manually yet.

After I did lose my SSH session, and reconnected, I have been able to do "ncs status", and only Database i running.

So I want to verify if something is goin on or not.

(Last time I did ncs start it corrupted the application, and required reinstallation of OVA)

Upgrade from NCS to Prime

Rob Johnson — Tue, 20 Aug 2013 12:15:51 GMT

Good Luck with it.

My money is on "you will need to do a ncs db reinitdb then start the restore out from scratch on the console port.

I've done quiet a few of the upgrades and that's what I resorted to in order to get it to work for me::::