WCS 7.0 migration to Prime?

We will upgrade the WLC from 7.0 to 7.3 to support HA, but looks like WCS does not support 7.3 code any more. We have lobby account on WCS to create the guest account for WLC. We then have to transfer WCS to another product-Prime.
My question is is this the only option? What prime component we have to choose-infrastructure or NCS?
thank you
Raymond

No there is a Prime Infrastructure 1.3 which has all 3 bundled together.
http://software.cisco.com/download/release.html?mdfid=284652876&softwareid=284272932&release=1.3&relind=AVAILABLE&rellifecycle=&reltype=latest
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Similar Messages

Migrate WCS 7.0.172 to Prime 1.3

Hi all,
I need to migrate from WCS to Prime in order to support WLC 7.4.
I'm a little bit confused about license migration procedure, I have read that it is necessary to move trought Prime1.2, so the license code that I need is:
R-W-PI12-M-K9
WCS 7.0 to Cisco Prime   Infrastructure 1.2 Migration
R-PI12-BASE-K9
Prime Infrastructure 1.2 Base   License and Software
L-PI12-LF-1K-LIC
Prime Infrastructure 1.2 -   Lifecycle - 1K Device Lic PAK
L-PILMS42-1K-M
Prime Infrastructure LMS 4.2 -   1K Device Upgrade Lic
L-W-PI12-1K-M
WCS to Prime Infrastructure 1.2   Migration 1K Device
How I can obtain .lic file for Prime from license present on my WCS installation?
The export from CLI procedure on WCS, export also the actual License?
Where is the procedure? I think there are some steps on the machine and others on the Cisco site
NOTE: I also change the position of the software from a virtual machine to another one
An additional request, in some document I read that it is possible to migrate directly to Prime1.3, is it true?
Thanks
Valerio

Has anyone seen an error message when trying to import WCS 7.0.230 maps into Prime Infrastructure 1.3.0.20?
WCS generated a .tar file, but when importing into Prime, it says:
XML Import: 'ImportExport_b8d18562d25d0f6f.tar' has an unsupported Mime Type. Mime Type sent by Browser: 'application/x-tar' Possible causes/workarounds: 1. Check File [Associations/Types/Extensions], 2. Ensure appropriate application launches file, 3. Try a different browser, 4. If File [Associations/Types/Extensions] are correct try closing the browser and relaunch. Supported file format mime types are 'application/gzip-compressed', 'multipart/gzip-compressed', 'multipart/x-zip-compressed', 'application/x-gzip-compressed', 'application/zip', 'multipart/zip', 'application/x-zip-compressed', 'multipart/x-gzip', 'application/x-zip', 'application/gzip', 'application/x-gzip', 'multipart/x-gzip-compressed', 'multipart/gzip', 'multipart/x-zip'

Migrate from Prime LMS to Prime Infrastructure

I'm currently running CiscoWorks LMS 4.0.1 on Windows 2003 under VMware and just got upgrade licensing for Prime Infrastructure 1.2. I am assuming that I will need to upgrade the current server to Prime LMS 4.2 in order to ensure that data migration to Prime Infrastructure goes well. I am planning to follow Cisco's recommendation to run Prime LMS and Prime Infrastructure in parallel for a time and migrate individual functions.
My real question is about Syslog handling. All of the managed devices are currently sending Syslog data to LMS. As a last step in the migration, is it possible to change the IP address of the Prime Infrastructure server to replace the Prime LMS server so that the Prime Infrastructure server will just start getting all the Syslog data, or do I need to go change hundreds of managed devices to point to a new address?
Thanks for any help you can provide.

Putting LMS up against Prime Infrastructure is like comparing Apples to Oranges.
LMS is a very mature product and Prime Infrastructure is in it infancy stages...
My suggestion would be to leave the current LMS system up and running; bring a Prime Infrastructure server up with a Demo License; add a few of each type of device to your Prime Infrastructure server; setup a proof of concept scenario to prove you can do everything in Prime as you can do in LMS.

Prime LMS EOL? Migration to Prime Infrastructure???

Hi All,
I'm a little bit confused about the support for Prime LMS 4.2.5... is there any date for end of Life/end of support for LMS?
Should customers migrate to Prime Infrastructure or what does cisco recommend???
best regards

Prime LMS 4.2 is not yet End of Sales or End of Life. Cisco continues to provide support develop minor device package updates etc. for it.
It will not get another major release going forward as strategically the platform being developed for wired and wireless LAN management is Prime Infrastructure (PI).
For existing LMS customers, they are encouraged to review the current feature comparison (link) and determine which product better serves their needs given that PI 2.2 does not have feature parity with Prime LMS 4.2.5. (Even new PI customers are given a license for Prime LMS in acknowledgement of this fact. How long that continues remains to be seen.)

WCS and LMS to Cisco Prime Infrastructure 1.3 Upgrade

Hello,
Our customer is currently having WCS for 500 devices and LMS 3.2 for 1500 devices. We are planning to upgrade to Cisco Prime Infrastructure 1.3.
I want to check is the upgrade procedure that we have planned is ok or we have missed something.
Phase 1: WCS to CPI 1.3 upgrade
1. Check that WCS is at 7.0.230.0 version
2. Export WCS database
3. Install NCS 1.1.1.24 software
4. Contact cisco to obtain trial license for NCS software (L-WCS-NCS1-M-K9 license).
5. Migrate WCS license and import it in NCS software
6. Migrate WCS data to NCS software using ncs migrate command
7. Patch NCS software
8. Inline upgrade to CPI 1.3 software
9. Install proper licenses on CPI 1.3 (WCS and LMS device count)
My concern in this first phase is should I use NCS large image since our Cisco Prime Infrastructure 1.3 software should manage 2000 devices at the end.
Or is it better not to perform inline upgrade and insted go with exporting data from NCS and then importing them to CPI 1.3 that is going to be installed separately?
Phase 2: LMS 3.2 to CPI upgrade
1. Export LMS 3.2 database
2. Install LMS 4.2 software
3. Install license to LMS 4.2
4. Restore data from LMS 3.2 to LMS 4.2
5. Direct upgrade from LMS 4.2 to 4.2.2
6. Export the device list with credentials from LMS 4.2.2 and import it as a Bulk Import in CPI 1.3
At the end we will have CPI 1.3 and LMS 4.2.2 software running.
Is it possible to directly upgrade from LMS 4.2 to LMS 4.2.4 and then import data to CPI 1.3 or we need to go with 4.2.2 version?
Regards,
Jelena

Hello Marvin,
We have restored LMS 3.2 SP 1 database on LMs 4.2 and we have got some error messages during restore. Please see our restore output:
[kalms4/root-ade ~]# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/res
resolver.pl           restoreDBTableMig.pl restoreJRMMig.pl      restorebackup.pl
[kalms4/root-ade ~]# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/BKP/
Restore started at : 2013/12/05 14:11:58
Please see '/var/adm/CSCOpx/log/restorebackup.log' for status.
     USER ID is ..................................... : sysadmin
     OS of the backup archive is..................... : Windows
INFO:The backup archive is from a different OS. Your current Platform is: Soft Appliance .
You are attempting to perform a Cross Platform Restore..
Do you wish to continue (Y/N) [Y] :Y
     Generation to be restored is ................... : 0
     Backup taken from............................... : /opt/BKP/
     Common Services version in the backup data is... : 3.3.1
     Common Services is installed in................. : /opt/CSCOpx
     The temp folder for this restore program........ : /opt/CSCOpx/tempBackupData
     Applications installed on this machine ......... : [Common Services][Campus Manager][Resource Manager Essentials][Device Fault Manager][cwportal][ipm][upm][cvw][cwlms]
     Applications in the backup archive ............. : [Common Services][Campus Manager][Resource Manager Essentials][Device Fault Manager][opsxml][cwportal][ipm][upm][cvw]
     WARNING: The list of applications installed on this CiscoWorks server does not match the list of
              applications in the backup archive. If you restore data from this backup archive,it may
              cause problems in the CiscoWorks applications.
              Do you want to continue the restore operation? (y-continue or n-quit, y/n)?Y
     Applications to be restored are................. : [Common Services] [Campus Manager] [Resource Manager Essentials] [Device Fault Manager] [cwportal] [ipm] [upm] [cvw]
     Available disk space in NMSROOT................. : 86451488 Kb
     Required disk space in NMSROOT.................. : 35906524 Kb
     (The temp and NMSROOT are on same device, therefore this required disk space includes temp space)
Copying the backup files to the temporary location [/opt/CSCOpx/tempBackupData]
preRestore of [Common Services] has started.
preRestore of [Common Services] has completed.
preRestore of [Campus Manager] has started.
preRestore of [Campus Manager] has completed.
preRestore of [Resource Manager Essentials] has started.
preRestore of [Resource Manager Essentials] has completed.
preRestore of [Device Fault Manager] has started.
preRestore of [Device Fault Manager] has completed.
preRestore of [cwportal] has started.
preRestore of [cwportal] has completed.
preRestore of [ipm] has started.
preRestore of [ipm] has completed.
preRestore of [upm] has started.
preRestore of [upm] has completed.
preRestore of [cvw] has started.
preRestore of [cvw] has completed.
doRestore of [Common Services] has started.
          Cross Platform Update started.
          Cross Platform Update completed.
          License check started.
             WARNING: The license details in the server are different from the backup data.
                      After restoring, please check the license available in the server.
             WARNING: Your current license count is lower than your earlier license count.
                      If you restore the data now, devices that exceed the current licence count
                      will be moved to Suspended state.
          License check completed.
          Restoring certificate.
             WARNING: Cannot evaluate the hostname, hence the certificate
                      may be from this host or another host.
                      [ Certificate not overwritten ]
          Restored Certificate.
          Restoring Common Services database.
          Restored Common Services database.
          Restoring CMIC data.
          Restored CMIC data.
          Restoring CMC data.
          Restored CMC data.
          Restoring Security Settings.
          Restored Security Settings.
          Restoring DCR data.
          Restored DCR data.
          Restoring Certificate key store.
          Restored Certificate key store.
Restoring DCNM CrossLaunch data.
          Restored DCNM CrossLaunch function.
          Restoring JAAS configuration.
          Restored JAAS configuration.
          JRM Job Migration started.
          JRM job Migration done.
doRestore of [Common Services] has completed.
doRestore of [Campus Manager] has started.
          Cross Platform Migration for Campus started.
Cross Platform update Starts for Campus
doRestore of [Campus Manager] has completed.
doRestore of [Resource Manager Essentials] has started.
10% of RME Restore completed
30% of RME Restore completed
50% of RME Restore completed
70% of RME Restore completed
100% of RME Restore completed
doRestore of [Resource Manager Essentials] has completed.
doRestore of [Device Fault Manager] has started.
10% of DFM Restore completed
30% of DFM Restore completed
50% of DFM Restore completed
80% of DFM Restore completed
Going to modify Eight PM report
Modified Sucessfully Eight PM report
100% of DFM Restore completed
doRestore of [Device Fault Manager] has completed.
doRestore of [cwportal] has started.
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.properties
Src file : /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db//portal.properties ,,, Destination file : /opt/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.properties
File Copied: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.properties
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.properties
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.script
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.script
Src file : /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db//portal.script ,,, Destination file : /opt/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.script
File Copied: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.script
Src file : /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db//portal.log ,,, Destination file : /opt/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.log
File Copied: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.log
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.log
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/db/portal.log
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties/defaultUserCommunity.properties
Src file : /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties//defaultUserCommunity.properties ,,, Destination file : /opt/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties/defaultUserCommunity.properties
File Copied: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties/defaultUserCommunity.properties
Src file : /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties//defaultCommunity.properties ,,, Destination file : /opt/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties/defaultCommunity.properties
File Copied: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties/defaultCommunity.properties
Error while coping the File: /opt/CSCOpx/tempBackupData/cwportal/CSCOpx/MDC/tomcat/webapps/cwportal/WEB-INF/classes/data/ciscoWorks/properties/defaultCommunity.properties
doRestore of [cwportal] has completed.
doRestore of [ipm] has started.
        10% of IPM Restore Completed
        30% of IPM Restore Completed
        50% of IPM Restore Completed
        60% of IPM Restore Completed
        70% of IPM Restore Completed
        100% of IPM Restore Completed
doRestore of [ipm] has completed.
doRestore of [upm] has started.
HUM database restore starts
INFO:STOP= /opt/CSCOpx/objects/db/bin64/dbstop -q -y -c dsn=upm
SQL Anywhere Command File Hiding Utility Version 10.0.1.4239
INFO: Database Shutdown is in Progress..Please wait
INFO: Stop Engine Args= /opt/CSCOpx/objects/db/bin64/dbstop -q -y -c dsn=upm
INFO: After Database Shutdown RC= 2304
root=C:\PROGRA~2\CSCOpx\databases\upm\upm.db
DBUTILS: Inside Cross Platform
INFO: Current Database password does not match the password of Database being restored
INFO: Using the Password of the Database being restored
HUM database restore successfully completed.
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Poller
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Poller/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Threshold
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Threshold/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Custom
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Custom/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Poller_Failure
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Poller_Failure/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/TrendWatch
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/TrendWatch/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Availability
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Availability/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/PoEPORTUtilization
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/PoEPORTUtilization/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Interface_Utilization
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Interface_Utilization/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Memory_Utilization
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Memory_Utilization/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Interface_Availability
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Interface_Availability/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Threshold_Violations
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Threshold_Violations/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/CPU_Utilization
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/CPU_Utilization/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/PoEPSEConsumption
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/PoEPSEConsumption/README.txt
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Interface_ErrorRate
File :/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/Quick/Interface_ErrorRate/README.txt
Directory is reportsStarted changing property .
linux
Restored HUM configuration file successfully.
doRestore of [upm] has completed.
doRestore of [cvw] has started.
doRestore of [cvw] has completed.
postRestore of [Common Services] has started.
postRestore of [Common Services] has completed.
postRestore of [Campus Manager] has started.
postRestore of [Campus Manager] has completed.
postRestore of [Resource Manager Essentials] has started.
postRestore of [Resource Manager Essentials] has completed.
postRestore of [Device Fault Manager] has started.
postRestore of [Device Fault Manager] has completed.
postRestore of [cwportal] has started.
postRestore of [cwportal] has completed.
postRestore of [ipm] has started.
postRestore of [ipm] has completed.
postRestore of [upm] has started.
postRestore of [upm] has completed.
postRestore of [cvw] has started.
postRestore of [cvw] has completed.
Restored successfully.
Are this errors going to affect our LMS 4.2 operations?
Then we have upgraded to LMS 4.2.2 and exported data and credentiales for PI import.
On PI 1.3 we have installed WCS 500 devices upgrade license and LMS 1500 upgrade license and now we are having 2000 devices lifecycle license. We have successfully restored WCS data in PI and we have imported LMS devices as bulk import. What is strange is that we have this message in prime regarding licensing:
On LMS 3.2 our customer had saved unlimited number of configuration versioning. After upgrading to LMS 4.2 we can only see last 3 configurations regardless of unlimided number of configurations in previous LMS, so my question is where can we find older configurations in LMS 4.2?
We are planning to turn unlimited versioning on CPI 1.3 now, so our customer will again have feature that they need. Do you have some experiance regarding disk space when all device configurations are stored forever?
Thank you for your help.
Regards,
Jelena

Migrated to Prime infrastructure and now the login on the server doesn't work

We have recently migrated from WCS 7.0.230.0 to Prime Infrastructure 1.3.0.20 and now there is a problem with logging in to our accounts. The problem can be broken down into two parts:
1. We can't logg in using radius (this is still working if we use the WCS or other applications using the same rule)
2. Unless we delete and recreate our accounts we can't even logg in locally
We have re-entered the radiusservers (they disappeared during the migration)
We have tried changing authentication form from pap to chap (in both ends) and then back again
Our radius servers are running Win2k8 R2
Any suggestions on how to solve this? We really need to get the domain-loggin working

mmm, i would say make sure that you have the attributes related to virtual domain appended to the list.
If you have already done that ,
may be you need to try the following:
Step 1)
Open https://NCSIPADDRESS/webacs/dbUpdateAction.do
With root username and password
Step 2)
Execute the Query as below
Query (1)
update WCSDBA.WCSPREFERENCE
set value='ROOT-DOMAIN'
where key ='defaultPartition' and username='a_user'
note-
username should be changed to whichever user is facing issues while logging in
Query (2)
commit work;
or to remove all entries in WCSDBA.WCSPREFERENCE except for SYSTEM, root or ALL_USERS:
delete from wcsdba.wcspreference where username <> '[SYSTEM]' and username <> 'root' and username <> 'ALL_USERS';
commit work;
Step 3)
Restart NCS after the commit changes and try logging back with 'a_user'
Please make sure to rate correct answers

Migrate from WCS 7.0 to Prime Infrastructure 1.2

Hi All,
I am looking for advice on the licensing and upgrade path for going from WCS 7.0 to PI 1.2.
At present I have a WCS licensed for 200 APs which is managing one controller and 150 APs.
I intend to use the Cisco Prime Upgrade Promotion
to order R-W-PI12-M-K9 (WCS 7.0 to Cisco Prime Infrastructure 1.2 Migration)
and L-W-PI12-100-M and L-W-PI12-100-M to match the number of licenses on the WCS.
Once Prime is installed I also want to manage another 50 devices, does that mean I have to purchase the
Cisco PI 1.2 Base License and Software (R-PI12-Base-K9) and another 50 Lifecycle licenses, or will
my existing 200 licenses from the upgrade suffice.
Sorry if it's confusing, but I didn't invent the licensing structure just trying to make sense of it all.
TIA

You'll be able to manage up to 200 devices/APs simpy using the upgrade from WCS to PI 1.2 as you described it. No need to order another base license or 50 lifecycle licenses.

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

WCS 7.0.240.0 data export to Prime 1.2.1.012 ... HELP!!

Hello Fellow Engineers,
I'm trying to migrate old data from WCS 7.0 to Prime 1.2 ... I have already created the zip file from WCS and imported it into the defaultRepo on Prime. I see it in the directory when I do a show repository defaultRepo so I have confirmed that it is there. My issue is that it appears Prime 1.2.1.012 won't accept the cli command of ncs migrate.
So, can someone let me know how I can proceed with the migration? I haven't been able to find any similar command in the Prime CLI so at this point I'm lost as to where I should go from here. I really don't want to have to tell the customer they have to downgrade to Prime 1.1 in order for them to perserve their maps especially since the Deployment Guide for Prime Infrastructure states that it is possible to migrate date from WCS 7.0 to Prime 1.2 as shown below ...
Data Migration
Data can be migrated from WCS 7.0, NCS 1.1, or LMS 4.x. More details on migrating data from each of these applications are spelled out in the following sections.
From WCS
You must upgrade the Cisco WCS server to one of the following releases before you attempt to perform the migration process to Cisco Prime Infrastructure 1.2:
• 7.0.164.3
• 7.0.172.0
• 7.0.220.0
This section provides instructions on how to migrate the WCS on either a Windows or Linux server to Cisco Prime Infrastructure.
Exporting Data from WCS
Export data from WCS 7.x through the CLI. The export userdata CLI command is available in WCS Release 7.x and later, which creates the ZIP file that contains the WCS data file. The CLI does not provide any option to customize what can be exported; all nonglobal user-defined items are exported. Complete these steps in order to export WCS data:
1. Stop the WCS server.
2. Run the export command through the script file and provide the path and export filename when prompted.
3. For Linux, run the export.sh all/data/wcs.zip command.
For Windows, run the export.bat all \data\wcs.zip command.
Importing Data into Cisco Prime Infrastructure
Complete the following steps to migrate data from WCS:
1. Place the WCS export ZIP file (for example, wcs.zip) in a repository or folder (for example, repositories).
2. Log in as the admin user and stop the Cisco Prime Infrastructure server by entering the ncs stop command. Configure the FTP repository on the Cisco Prime Infrastructure appliance using the repository command as shown in configuration snippet below:
pi-appliance/admin# configure
pi-appliance/admin(config)# repository pi-ftp-repo
pi-appliance/admin(config-Repository)# url ftp://209.165.200.227/backup
pi-appliance/admin(config-Repository)# user ftp-user password plain ftp-user
Note: Make sure the archived file is available with the show repository <repositoryname> command.
3. Enter the ncs migrate command in order to restore the WCS database.
pi-appliance/admin# ncs migrate wcs-data wcs.zip repository pi-ftp-repo
4. By default, no WCS events are migrated. Enter the ncs start command in order to start the Cisco Prime Infrastructure server after the upgrade is completed. Log in to the Cisco Prime Infrastructure user interface with the root login and the root password.
Any HELP on this would be greatly appreciated!!!
Thanks in advance!!!!

Scott,
I don't have a FTP client ... I typically use TFTPd for any upgrades I have to do. I thought I could use this to transfer the patch and export.zip to NCS? However, when I tried to run the patch install it gives me this error ...
% Manifest file not found in the bundle
Can you tell me if you have experienced this before? Also if it's a problem with me using TFTPd can you recommend a FTP client application that I should use.
Thanks!

Prime LMS 4.2 to Prime Infrastructure 2.0 license migration

A couple of months ago I upgraded WCS to Prime Infrastructure (WCS via NCS to PI 1.2 at that time). Meanwhile PI is running version 2.0. For some reason, when purchasing the upgrade licenses, I also got a 500 device LMS4.2 upgrade license.
The exact part numbers were:
R-W-PI12-M-K9 WCS 7.0 to Cisco Prime Infrastructure 1.2 Migration
R-PI12-BASE-K9 Prime Infrastructure 1.2 Base License and Software
L-PI12-LF-500-LIC Prime Infrastructure 1.2 - Lifecycle - 500 Device Lic PAK
L-PILMS42-500-M Prime Infrastructure LMS 4.2 - 500 Device Upgrade Lic
I have a virtual LMS appliance running where I installed the 500 device license I mentioned. I've actually never used LMS but that's a different story...
As I'm running low on PI device licenses (lifecycle licenses to be precise), the question is:
Is there an officially supported scenario to migrate these 500 LMS 4.2 licenses (that are already the result of a license upgrade) to PI 2.0?
If so: what part numbers do I need to purchase? I suppose I need
R-L-PI2X-U-K9 LMS to Cisco Prime Infrastructure 2.x Upgrade
plus
(L-L-PI2X-500-U LMS to Cisco Prime Infrastructure 2.x Lifecycle Upgrade 500 Device)
XOR
(L-L-PI2X-500-UP LMS to Cisco Prime Infrastructure 2.x Lifecycle Upgrade with PASS 500 Device)
Maybe someone can comment on that... thanks in advance.

In case anyone is facing the same issue:
Meanwhile, I finished the upgrade process using the following part numbers:

WCS to Prime 1.2 licensing

Hi
I am doing a migration from WCS 7.x to Prime 1.2
There is a WCS 7 to Prime 1.2 migration license pack that we have obtained.
However, as I understand it, we need to install NCS 1.1.1.24 first, import the WCS database and then carry on to do the NCS to Prime upgrade. So we have the licenses for the final Prime 1.2 deployment.
When we get to NCS 1.1.1.24 we cannot migrate off of the main login page until we apply an appropriate NCS license. We were told by Cisco Sales that a temporary license can be generated for NCS 1.1.1.24 by sending licensing the license XML file taken from WCS along with the VUDI and our license order info. We have followed this path successfully once. We sent the XML file to Cisco along with some other info and they returned a license we could use on NCS. We then moved to Prime 1.2. However on this occasion Cisco insist we need an NCS license.
I have moved from NCS 1.x to Prime 1.2 before and all the licenses have been retained.
So are Cisco telling me that to migrate from WCS 7 to Prime 1.2 I should license the NCS server and simply upgrade it to Prime 1.2 with no further licensing needing purchased ? If so why is there a WCS to Prime 1.2 license pack ?
Or are Cisco saying we need the NCS license AND the Prime 1.2 licenses ?
Thanks for any input, St.

Thanks for this too Scott.
I see that you could license NCS 1.1.1.24 then move to Prime 1.2 without applying further licenses. I have done this in a NCS to Prime upgrade. Prime maintains the NCS licenses. However there is a WCS to Prime 1.2 License SKU which we have ordered because we are starting from WCS on this occasion. The licenses generated from these PAKs do not work on NCS 1.1.1.24
So it would seem that the WCS to Prime migration SKU does not include the necessary license to allow us to pass through NCS 1.1.1.24 during the migration.
I think if we had ordered a WCS to NCS migration SKU we would have got the necessary NCS license. We could then install that and carry on to Prime 1.2 with no further license requirements. If that is the case why is there a WCS to Prime 1.2 migration SKU ?
We did resolve this issue before by following the advice of Cisco Sales. We logged a call with licensing, supplied the exported WCS license XML file and the NCS VUDI and they gave us an NCS license. However, on this occasion licensing are not so forthcoming. They suggest we need a NCS 1.x licence.
So either they are implying we need a NCS 1.x AND a Prime 1.2 license. Or we should have bought a WCS to NCS migration license and the NCS to Prime migration license is useless because it does not allow us to pass through NCS as part of the migration process.
Thanks for any help on this, St.

Upgrading WCS 7 to Cisco Prime (CPI) 2

Hello,
I have read a few article and posts about upgrading WCS 7 to CPI 1.2 via NCS. However now with Prime 2.0 I was hopping I didn't have to use NCS.
I can't find any migration guides or documents about migrating to 2.0 instead of 1.x.
Can anyone point me in the right direction.

Direct migration from WCS 7.x to Cisco Prime Infrastructure 2.0 is NOT possible.
in my work I had this problem.
the only solution was to first install the NCS 1.1, after the patch 1.1.1.24 and then migrate to 2.0
Backup WCS data , upgrade to NCS 1.1 and restore de data...
install patch 1.1.1.24 , only then you can do the upgrade to version 2
CISCO:
"We strongly recommend upgrading your WCS to 7.0.230.0 (for data integrity) or higher before attempting to migrate to NCS.
Users will first need to do an intermediary migration to NCS 1.1.1.24, and then do an inline upgrade (or migration) to Cisco Prime Infrastructure 2.0"

Cisco Prime 2.1 to Prime 2.2 Migration

Hi All,
I would like to share my Migration experience from Cisco Prime 2.1 to 2.2.
Just to let you know, After several hours trying to migrate properly from Cisco Prime 2.1 to Prime 2.2 with no success; The conclusion is; to migrate from Prime 2.1 to 2.2 successfully. The migration need to be executed in a specific order so it can work properly.
The sequence is as follows:
Deploy in the VMware environment the new Prime 2.2 OVA file exactly as Prime2.1 hardware requirements.
Restore you Application backup from Prime 2.1 into Prime2.2.
Run update Cisco Prime Infrastructure 2.2 - Maintenance Release 1 pi221_20150131-27.ubf
Run update Prime Infrastructure 2.2 - Device Pack 3 pi_2.2_device-pack_3-31.ubf
Run update Wireless Technology Pack - Converged Access and Meraki support. Must have 2.2.1 maintenance release installed. Wireless_Technology_Pack-2.2.1.0.0.30.ubf
Good luck....

Hello i have finally
uninstalled prime lms4.2.0 , an then
reinstalled,without changement on the windows sytem.
and then i have restored databases.
the i could install patch prime lms4.2.2
and then 4.2.4
and finaly it works fine !

Migrating from Cisco Prime Unified Provisioning Manager 9.0 BE to Prime Collaboration 9.0 Provisioning

Hi All,
    Cisco BE 6000 9.X support both Cisco Prime Unified Provisioning Manager 9.0 BE and Prime Collaboration 9.0 Provisioning as its management tool. OVA for both applications are pre-loaded on server from factory starting end of March 2013.
    For some customers that start with Cisco Prime Unified Provisioning Manager 9.0 BE, and want to migrate to Prime Collaboration 9.0 Provisioning for advanced features, they can follow the following guide for migration.
http://www.cisco.com/en/US/partner/docs/net_mgmt/prime/unified_provisioning_manager/9.0BE/migration/guide/migrate_90be_pc90.html
    For more collaterals for Cisco Prime Collaboration, please visit
http://www.cisco.com/en/US/partner/products/ps12363/index.html
Best
Jing

Finally, the solution of the problem was:
1-stop the daemon manager “net stop crmdmgtd”
2- Delete the xml files available under(please take backup from them) :
CSCOpx\objects\sir\work
CSCOpx\objects\topo\work
3-Start the daemon manager net start crmdmgtd (wait for 20 minutes until all process are up )

WCS licences into prime 2.1

I have WCS running version 5.2.148.0 .. It has 450 base licences .
I have now got Prime running at version 2.1
Is there a way of taking the 450 base licences from WCS and import them into prime 2.1 as device licences ???
I aslo have the software assurance plan from cisco !!
regards

That is not the supported method to make you eligible to retain the 450 WCS licenses as PI Lifecycle licenses. SASU for the WCS product would include that eligibility.
SASU for PI only covers the Base plus any Lifecycle and Assurance licenses purchased with your Prime Infrastructure.
You partner should be able to confirm this using both the Cisco Commerce Workspace (CCW) ordering tool and the PI BOM builder (the latter available in the Partner Community)

WCS 7.0 migration to Prime?

Similar Messages

Maybe you are looking for