Migrate WCS V 7.0.240 to NCS V 2.0.0.0.294

Hi everybody:
Some months ago , i had to upgrade our WLCs to the version 7.4.110, but the WCS doesn´t support these WLC ios version, then i decide to migrate to the NCS, i found some docs that explain that NCS v .20 supports these IOS WLC version, my question is, somebody know the procedure to migrate the WCS licenses to NCS
I exported the licenses to a new NCS but it didn´t accepted, show me and error that the file is not appear a license file.
I have a licenses files ( .lic) and the system show me an error that UDI of file does not match the system, i understand tha when you create license file, the name of the server is associated to the license.

take a look at the below link for the license portion:
http://jenniferhuber.blogspot.com/2012/03/wcs-to-ncs-migration.html?showComment=1343851642987#c6457428309941635205
HTH,
Steve

Similar Messages

Unable to Migrate WCS Database to NCS with Demo License

I have NCS 1.1.0.58 running on a VM with a demo license, should I be able to migrate my WCS 7.0.230.0 database to NCS? I can not tell if the migration process worked and there are no objects in NCS. I have attached a console capture of the migration console messages.
Thanks in advance,
Bob

You have probably thought of this already but, If the tables are the same in both sides why don't you just work out the population order and export directly from Access into the empty oracle tables using ODBC?
The way I do it is to create transition tables in oracle then have a script to load the tables and do some validation and error checking.

Migrating WCS Data to NCS

Hi,
I've been trying to migrate in my exported data from WCS to NCS as per the release notes but its not working for me.
We generated a licence from the UID and serial number for our VM install of NCS. I see mention of upgrade licenses do i need one of those?
Do I have to import the license separately from WCS. I thought that the export would include license + data.
I thought this would be straightforward but it doesn't seem that way. Is there anything that I'm leaving out or that i need to do to get this migration work.
Attached output from migration.
All help greatly appreciated.

Hi Scott,
It was a licensing issue and we've finally resolved that. So i now have all our AP licenses imported into NCS.
I have run the migration again for the WCS data to be imported and it doesn't seems to have worked or is there something else i've to do. According to the release notes it just tells you to log in after the migration.
Any ideas?
Anthony
=================================
Forgot to get back to you on this one Scott. The license was the main issue afterwards I just had some problems with tftping the data from the WCS to NCS servers. Resolved that then.
Thanks.
Anthony

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'

Migration WCS to Prime 2.2

Hi,
A Customer of mine has three instances of WCS he wants to upgrade to Prime 2.2.
Regarding the upgrade path there are several steps. If we have to follow this path three times
this takes at least three days of work.
I wonder if there is a way to rehost the WCS licenses to Prime 2.2.
Another question is, if the maps exported out of WCS contain the AP positions and if they
can be imported into Prime 2.2.
Regards,
Urs

Hi,tsgruu2000.
Sorry to say that you cannot rehost the WCS licences to Prime 2.2. You need to purchase new license for the Prime once you upgrade it. For further assistance kindly email me directly at ([email protected])
Happy to Serve!
Barry

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

WCS database export for NCS migration

Hi
I have done a WCS 7.0.220.0 to NCS migration prior to moving to Prime 1.2. I followed the instructions to export the WCS database via the export.bat all command and exported the database. However, when I import this zip fileto NCS there do not seem to be any of the original WCS templates. All the maps and AP details have migrated but no templates.
I have tried the export again and ploughed through the resultant zip file looking for anything that looks like template files but there is nothing immediately apparent that looks like templates.
Has anyone done this before and successfully migrated their original templates ?
Many thanks, St.

The templates should of migrated. These are the only data that isn't migrated.
Non-upgradable Data
The following data are not upgradable from WCS to NCS:
• Certain Reports (Client Count, Client Summary, Client Traffic, PCI Report, PCI Compliance Detailed and Summary reports, Preferred Call Network Summary report, Rogue APs, Adhoc Rogues, New Adhoc Rogues and Security Summary reports).
• Dashboard customization
• Client Station Statistics information will not be populated with old WCS data in clients charts, client details page, dashboards and reports.
• Client historical session information does get upgraded.
• All events from 7.0 are completely dropped and are not migrated to NCS.
• RADIUS/TACACS server IP and credentials are not migrated and need to be readded again after migration is complete.
Sent from Cisco Technical Support iPhone App

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!

NCS 1.1.1.24 migration to PI 1.2.1.012

I have an open TAC case on this also....but it's taking longer than usual for them to get pertinent info back to me so figured I'd try here.
I'm in the process of migrating from WCS to Prime Infrastructure 1.2 I've already sucessfully completed the WCS -> NCS 1.0.x upgrade, and then the NCS 1.x to 1.1.1.24 upgrade with no issues. I've followed the suggested migration path to PI 1.2 of deploying a new OVF and them migrating the NCS data from the NCS virtual machine to the new PI virtual machine.
I have PI 1.2.1.012 installed in a new VM and up and running with correct licensing. I installed the "ncs_patch-1.1.1.24-upgrade-12.tar.gz" patch on my NCS install before exporting my data from NCS (and rebooted). NCS data was exported using:
backup ncs-backup repository remoteRepo application NCS
Now when I go to import that data into the PI 1.2.1.012 appliance I get the following:
pi-01/admin# restore ncs-backup-130131-1333.tar.gpg repository remoteRepo application NCS
Restore may require a restart of application services. Continue? (yes/no) [yes] ? yes
Initiating restore. Please wait...
Stage 1 of 9: Transferring backup file ...
-- complete.
Stage 2 of 9: Decrypting backup file ...
-- complete.
Stage 3 of 9: Unpacking backup file ...
--complete.
Stage 4 of 9: Decompressing backup ...
-- complete.
Stage 5 of 9: Restoring Support Files ...
-- complete.
Stage 6 of 9: Restoring Database Files ...
-- complete.
Stage 7 of 9: Recovering Database ...
Failed to restore the DB. Exception: java.lang.Exception: RMAN-00571: ===========================================================
pi-01/admin#
I found bugID CSCub35534 which shows the same "RMAN-00571" java exception error so I might be running into this bug. I followed step 1 in the bugID of stopping my NCS 1.1.1.24 services (ncs stop) and then exporting my data from NCS again, and re-import into PI. Still have the same problem.
Dumping the logs from PI to a remote repository and looking at them doesn't give me much more info. I can see the "Failed to restore the DB. Exception: java.lang.Exception: RMAN-00571:" error in the log file but not much more info that I can figure out around it to determine what's going on.
I've used the PI 1.2 upgrade docs as well as this document through this whole process:
https://supportforums.cisco.com/docs/DOC-26972
Anyone else run into this exact same problem? How were you able to work around this and get you data imported in PI 1.2?
--greg

Finally got this working last evening! Not 100% sure exactly what I did but the restore was sucessful. I think it might have had something to do with making sure that NCS was not running when trying to restore the data. I didn't see any references in any of the documentation to make sure NCS was complete shut down (ncs stop, and ncs status to verify) before doing the restore. But after several db reinit's it appears to have restored everything properly now. For future reference here's what I ended up doing starting with WCS (Linux version):
Make sure WCS was running the latest version v7.0.230.0
Export maps from WCS via the GUI (as a precaution -- we have way too many maps to redo all them again!):
In the GUI go to Monitor -> Maps
Select which maps you want to export (you can select them all)
Select Export Maps and tell it where to store the export
Stop WCS from the cli: /opt/WCS7.0.230.0/StopWCS
Export your user configuration from WCS:
: /opt/WCS7.0.230.0/export.sh all /root/wcs-export-TODAY.zip
Copy the backup file off to another SCP/FTP server
Deploy the NCS 1.1.1.24 OVM (NCS-VA-1.1.1.24-xxxx.ova) template and get connectivity working to the VM
STOP the NCS services!! Then verify all services have stopped:
ncs stop
ncs status
Create a repository where you stored your WCS backup:
configure terminal
repository wcs-backup-repo
url sftp://xxx.xxx.xxx.xxx/home/user/wcs-backups/
user myusername password plain mypassword
exit
Verify you can see the files in the repository:show repository wcs-backup-repo
Migrate the WCS data into NCS (this will take a LONG time to run!):ncs migrate wcs-data wcs-export-TODAY.zip repository wcs-backup-repo
Start NCS if import was sucessful:ncs start
Verify everything looks good (no errors, all devices show up, maps are there etc)
Download the NCS 1.1.1.24 to Prime Infrastructure 1.2 patch and save it in the same repository as your WCS backup files
Stop NCS and verify all services have stopped:
ncs stop
ncs status
Install the NCS 1.1.1.24 to Prime Infrastructure 1.2 patch:
application upgrade ncs_patch-1.1.1.24-upgrade-12.tar.gz wcs-backup-repo
Reboot the appliance:reboot
Verify that patch was installed (it should show the upgrade-12 patch is installed):show application version NCS
Stop NCS and verify all services have stopped:
ncs stop
ncs status
Export the NCS application data:backup ncs-export-TODAY repository wcs-backup-repo application NCS
If you are deploying a brand new Prime Infrastructure v1.2 appliance (as suggested by the release notes), deploy the new PI v1.2.1.012 OVM and get connectivity working to it.
Create the repository what contains your backup files:
configure terminal
repository wcs-backup-repo
url sftp://xxx.xxx.xxx.xxx/home/user/wcs-backups/
user myusername password plain mypassword
exit
Make a local directory on the PI appliance for the local repository:mkdir disk:/defaultRepo
Create a local repository on the PI appliance:
configure terminal
repository defaultRepo
url disk:/defaultRepo
Verify the repositories (defaultRepo should be empty):
show repository defaultRepo
show repository wcs-backup-repo
Stop NCS and verify all services have stopped:
ncs stop
ncs status
Import the data from NCS into PI (this will take a LONG time to run!):restore ncs-export-TODAY.tar.gpg repository wcs-backup-repo application NCS
Restart NCS services and verify they are running:
ncs start
ncs status
Verify you can login and all data has been imported. Hopefully you are all good!
If things go wrong these are some additional commands that might help:
If the database on the appliance you are trying to import data to appears to have something wrong you can try doing this (NOTE all local disk: repositories will lose the data/files!):
ncs stop
ncs status
ncs cleanup
ncs start
ncs status
If there is still something wrong with the database you can try re-creating the NCS database from scratch on the appliance (NOTE YOU WILL LOSE EVERYTHING IN THE DATABASE WHEN DOING THIS!):
ncs stop
ncs status
ncs db reinitdb
ncs start
ncs status
If you know your linux commands you can also gain true bash shell access to the underlaying system by enabling the root account and setting a password for it:
root_enable
Enter the password you would like to give the root account
root
NCS log files and other goodies are located in the /opt/CSCOlumos/ directory. I found lots of troubleshooting data in there, as long as your good with navigating around the directory structure and reading the logs you should be able to figure out ecactly what might be going on.
Good luck to everyone in their quest to get to the latest version! Cisco definately did not make this process an easy one.
--greg

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.

WCS upgrade to Prime Infrastructure 1.3

According to this doc:
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps12239/deployment_guide_c07-721232.html#wp9000642
I can upgrade directly from WCS to PI 1.3. This doesn't seem to be the case, the "ncs migrate" command does not exist. Looking over other posts it seems i should setup a demo version of NCS, migrate WCS data to it, then export to PI. Problem is, the demo version of NCS is no longer on the Cisco site for download. I opened a TAC case, but I have a feeling i won't hear anything for a while, thought i'd check here to see if anyone else has a suggestion.
Thanks!

http://software.cisco.com/download/release.html?mdfid=284206374&flowid=30982&softwareid=283927263&release=NCS%201.1.3&relind=AVAILABLE&rellifecycle=&reltype=latest
Pull your version from the link above.
Licensing NCS 1.1.1.24 won't be necessary to import the wcs data using the ncs migrate command
and the backup command used to get a backup from the NCS system.
Be sure to install Path 12 before running the ncs migrate command....

Demo license of NCS

Hi,
I am migrating WCS to PI 1.3.
I read from the guide that we need to migrate to NCS 1.1.1 first and we can get the demo license from Cisco.
but the demo license is only 100 unit, but my WCS has 300 license units.
How can I import the wcs data to NCS?
Besides, I also read from the guide that I need to install patch in NCS before migrating the data to PI 1.3
can I install the patch before i import the data from WCS?
thanks.

I never used a demo license when doing a migration. Typically you need the same ap license when migrating but all NCS will do is complain. As far as the migration goes, install the license prior to doing anything. Export the WCS which needs to be on 7.0.220.0 or later and then import that to NCS. Then you need to patch NCS before upgrading to Prime infrastructure. Now when you get your license, you will need to order the prime license. If your using a VM, make sure you take a snapshot before you install the patch and upgrade just incase something failed or else you will be rebuilding NCS and importing the data again.
Sent from Cisco Technical Support iPhone App

Do we have any documentation describing the process a customer would have to follow to consolidate multiple WCS systems into 1 PI?

Do we have any documentation describing the process a customer would have to follow to consolidate multiple WCS systems into 1 PI?

NCS release notes provide details on migrating multiple WCS servers to NCS, which then can be upgraded to PI.
http://www.cisco.com/en/US/docs/wireless/ncs/1.1/release/notes/NCS_RN1.1.1.html#wp298961

WLC Audits on WCS - Configuration names question

Hi Everyone,
I've been clearing up the config differences between my WCS and the WLCs and for the most part I've identified what each line in the audit report refers to. However the following has me stumped:
Configuration Name Audit Status Attribute Value in WCS Value in Controller
150.3.40.240/1 Mismatch interval 1 10
150.3.40.240/4 Mismatch interval 1 10
150.3.40.240/5 Mismatch interval 1 10
150.3.40.240/6 Mismatch interval 1 10
150.3.40.240/7 Mismatch interval 1 10
150.3.40.240/8 Mismatch interval 1 10
150.3.40.240/9 Mismatch interval 1 10
150.3.40.240/10 Mismatch interval 1 10
150.3.40.240/11 Mismatch interval 1 10
150.3.40.240/12 Mismatch interval 1 10
150.3.40.240/HR Not Present In WCS - - -
150.3.40.240/OM Not Present In WCS - - -
150.3.40.240/PK Not Present In WCS - - -
150.3.40.240/EG Not Present In WCS - - -
150.3.40.240/KZ Not Present In WCS - - -
150.3.40.240/BH Not Present In WCS - - -
150.3.40.240/VN Not Present In WCS - - -
150.3.40.240/EC Not Present In WCS - - -
150.3.40.240/KW Not Present In WCS - - -
150.3.40.240/PY Not Present In WCS - - -
150.3.40.240/PR Not Present In WCS - - -
150.3.40.240/CR Not Present In WCS - - -
150.3.40.240/DO Not Present In WCS - - -
It would be really easy to just do a "restore values from controller" to reslove the differences but I'd really like to find these within the configuration pages in order to increase my understanding of the CUWN.
Can anyone tell me what these entries are?
Many Thanks
Scott

Hi Sam,
Is that relevant? I was really looking for the location of these configuration options/parameters within either WCS or the WLCs.
thanks
Scott

Problem audit mismatch WCS/WLC for local net user

HI,
I have a problem in my WCS the audit status is mismatch for my two controllers. When I see the details of the mismatch, it is said that all my 400 users are "not present in controller".
However, I checked directly on my web interface of my controllers and my users are there (Security--> AAA--> Local Net Users). I've also checked on the WCS (ConfigureàControllersà controlerà Security à AAA -> local net user).
In both My users are present and are identical.
When i refresh config from controllers on the WCS it disappears but a week after the mismatch comes back.
If anyone can help, Thanks
Alex

Anyone able to answer this one?
We are having the same issue. We had WLC code 7.0.116.0 with WCS giving us mismatches on certain thresholds, despite the fact that the controller and the WCS configs were a match and no one made changes. We would refresh confgi from controller and a week later, the mismatch was back. It's as if there was something wrong with the WCS database. We upgraded to NCS 1.1 and are now on WLC code 7.0.230.0 and it worked for a while, but we are now randomly experiencing the same issues and then some with NCS.
We have a multi-tenant campus that has several of another organizations access points configured as friendly in NCS, but the controllers still had them as rogue and were containing them. We are also experiencing a max client count threshold that is set to 20 on the controller, but NCS is now reverting back to the default 12 value and giving off a mismatch. I don't know if there is a SQL issue with the database or not, but we service roughly 3000 users on a 5 million sq. ft. campus and some of these mismatches and failure to identify critical mismatches is starting to become a problem. Going to open a TAC case, but if anyone has any insight in the mean time, that would be helpful. Thanks!

Migrate WCS V 7.0.240 to NCS V 2.0.0.0.294

Similar Messages

Maybe you are looking for