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

Similar Messages

  • WCS upgrade to Prime 1.2

    I'm currently running WCS 7.0.230 ready for upgrade to Prime 1.2. Reading Cisco docs, the path is to upgrade from WCS to NCS 1.1.1.24 firstly, then to Prime 1.2
    so far...
    export.bat all > wcs-export.zip
    also performed a backup via the GUI backup tool
    have a NCS 1.1.1.24 - 30 day eval license (docs say eval is enough before upgrading to Prime 1.2 which you have purchased)
    A couple of things are not clear to me,
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/quickstart/guide/cpi_qsg.html#wp56675
    currently WCS runs
    7.0.230
    Feature - plus
    AP limit 150
    Type permanent
    Does this mean I need to uninstall WCS to install NCS cleanly or is there an upgrade path without uninstalling WCS manually? In the download section you can only download  for Small/medium/Large. I intend to download medium, but again there are no specifics I can find in relation to my WCS license i.e. - AP limit = NCS medium or do I look at my new Prime License 500 Device upgrade LIC
    I'm looking for better documentation WCS > Prime.

    I manged to upgrade to NCS 1.1.1.24 without any problems and successfully migrate the WCS backup file into NCS.
    The next issue I have is upgrading from NCS 1.1.1.24 to Prime 1.2.
    Performed NCS backup successfully
    admin# show repository defaultRepo
    backup-20130422-0950.tar.gpg
    PI-upgrade-bundle-1.2.1.12.tar.gz
    Upgrade not successful (i'm still running NCS eval license, should I be importing Prime PAK licenses after upgrade to Prime?)
    admin# application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz defaultRep                                                                              o
    Save the current ADE-OS running configuration? (yes/no) [yes] ?
    Generating configuration...
    Saved the ADE-OS running configuration to startup successfully
    Initiating Application Upgrade...
      Stage 1 of 7: Transferring file ...
      -- complete.
      Stage 2 of 7: Unpacking file ...
      -- complete.
    % One or more required RPM's not found in the bundle
    admin# show ver
    Cisco Application Deployment Engine OS Release: 2.0
    ADE-OS Build Version: 2.0.1.038
    ADE-OS System Architecture: x86_64
    Copyright (c) 2005-2010 by Cisco Systems, Inc.
    All rights reserved.
    Hostname: SV195968
    Version information of installed applications
    Cisco Prime Network Control System
    Version : 1.1.1.24

  • Upgrade Cisco Prime Infrastructure 2.1.1 to 2.2

    Hi,
    I would like to know how to
    1. Upgrade Cisco Prime Infrastucture 2.1.1 to 2.2 procedure
    2. How to backup existing config and data
    Thanks in advance
    - nazir

    Hi Nazir,
    Refer the below link  for the upgrade from the exiting version ::
    http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/quickstart/guide/cpi_qsg.html#pgfId-113783
    Follow the same steps :
    Step :Backup  on 2.1  
    Step 2: Restore  2.2
    Backup and Restore::
    Backup command::
    PIServer/admin# backup MyBackupFileName repository MyRepo application NCS
    Check the below link for
    http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1/administrator/guide/PIAdminBook/backup_restore.html#pgfId-1080733
    Step ::
    Once Backup is completed , you need to Restore the backup to the Newly Buid PI 2.2 server::
    Restore command:
    PIServer/admin# restore filename repository repositoryName application NCS
    Check the below link:
    http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1/administrator/guide/PIAdminBook/backup_restore.html#99810
    Thanks-
    Afroz
    ***Ratings Encourages Contributors ****

  • SCP IOS Image Upgrades in Prime Infrastructure 2.1 Failing

    Hi I'm running PI 2.1 with all the latest patches and packs but I can't get SCP Image transfers to work.
    When I check the suggested logs from the Jobs Dashboard (and jump into the CLI root)  I see the following:
    [SWITCH-DEVICE]=Switch Hostname
    [SWITCH-ADMIN-LOGIN]=Level 15 username login to Switch, same username the is used in the Device Work Centre
    [PRIME-INF-IP]=Prime Infrastructure Server
    [SWITCH-DEVICE]#archive download-sw ............... archive download-sw /allow-feature-upgrade  
    /overwrite scp://[SWITCH-ADMIN-LOGIN]@[PRIME-INF-IP]//localdisk/tftp/c3560-ipbaselmk9-tar.122-55.SE9.tar
    Password:
    Password:
    % Authentication failed.
     Could not buffer tarfile...using multiple downloads
    examining image...
    Password:
    Password:
    % Authentication failed.
    %Error opening scp://[SWITCH-ADMIN-LOGIN]@[PRIME-INF-IP]//localdisk/tftp/c3560-ipbaselmk9-tar.122-55.SE9.tar (Permission denied)
    %Error opening flash:update/info (No such file or directory)
    ERROR: Image is not a valid IOS image archive.
    [SWITCH-DEVICE]#
    It looks like the switch is trying to log into the PI server and download the software as opposed to PI sending the software to the switch.
    I've used WinSCP to open up the URL, but none of the passwords I know or created work.
    Do I need to SSH into the PI box and create a new CLI account (or Root CLI account) that matches up to the switch [SWITCH-ADMIN-LOGIN]?
    Regards,

    Hi rowansakul,
    The work around for this particular issue involves having a user set up in the root cli and then from the the GUI navigate to Administration > System Settings > Image Management and set up the SSH Username with your new user account that you created under root cli.  That is the credentials that Prime is looking for when it is attempting to access its own image repository.
    Regards,
    Brandon

  • Upgrading from LMS 4.1 to Cisco Prime Infrastructure

    Looking for some information and confirmation on the upgrade process.
    Currently we are running LMS 4.1 with a valid SAS Service Contract which will allow me to upgrade to Prime Infrastructure 1.1 or Prime Infrastructure 1.2 using the upgrade tool at no charge. After using the tool I am given access to download PI1.1 or PI1.2, however, it only actually let me download PI1.1 but said i do not have the proper permissions to download the 1.2 license. I also noticed that the software images for 1.2 are not available ont he ciso download page.
    I am wondering what the latest version of Prime Infrastructure I will be able to upgrade to without an additional purchase. Can I upgrade up to all the way up to 1.4 or can I only go up to 1.2 (but then where is the download for the software).
    If i can upgrade to 1.4 then what path should I take? 1.1 to 1.3 to 1.4? Just skip 1.2 since the download is not available and it will not let me download the license file?
    Thank you for your help

    LMS 4.x to Prime 1.x would not be considered a functional or recommended "upgrade" for most intents as you would lose several major capabilities (Topology, Ciscoview, many reports, compliance templates, etc.). Your best path right now would be to move your LMS along to the current version - 4.2.4. The release notes explain the upgrade path for that.
    Licensing and upgrade eligibility-wise you need SASU for PI (not plain SAS for LMS) for major upgrades (i.e to go to 2.0). An LMS SAS contract entitles you to migrate to PI 1.2 which in effect means 1.3 although Cisco had some issues with updating the ordering system so there was not actually a SKU for PI 1.3 sold - only the 1.2 version which, when combined with your LMS SAS service contract, entitles you to move to PI 1.3 (or 1.4 but that's not generally recommended). More details are in the Prime Ordering and Licensing Guides here.
    Personally, I recommend customers with existing LMS 4.x installations wait until PI 2.1 comes out to consider the upgrade. 2.0 still misses several tools present in LMS 4.x.
    If you really want to move over to PI, you can export the data from LMS 4.2.4 and import into PI 1.3 (or 2.0).

  • Cisco Prime Infrastructure 1.3 to 2.1

    I have a Cisco Prime Infrastructure version 1.3 virtual appliance and we have a new Prime Infrastructure version 2.1 virtual appliance set up. I would like to get the wireless information put into the new server. This includes the WLC and APs and then the campus maps and the location of each AP on the map Im not sure if the heat mapping is a feature of Prime or if I have to set that up too. But I would like the heat maps.
    What would be the easiest way todo this?

    Are you logged in with a cisco.com (CCO ) userid? I just checked it and it works fine for me.
    You can navigate down to it via:
    HOME
    SUPPORT
    PRODUCT SUPPORT
    CLOUD AND SYSTEMS MANAGEMENT
    CISCO PRIME INFRASTRUCTURE
    INSTALL AND UPGRADE
    INSTALL AND UPGRADE GUIDESCisco Prime Infrastructure 2.1 Quick Start Guide

  • LMS 4.0 and Prime Infrastructure..!

    Hi,
    I am using LMS 4.0 and as the licenses got expired I came to know that I need to buy Prime Infrastructure license as LMS 4.0 reached End of life.
    So now if I buy the prime infrastructure licenses, will it work on LMS 4.0 or I need to upgrade? and how can I get the upgrade?
    Thanks..!

    You would need to upgrade.  Prime Infrastructure 1.2 has LMS and WAN buildt in.
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • Cisco Prime Infrastructure 2.0 and ASA 55xx platform

    Hello,
    We recently upgraded to Prime Infrastructure 2.0 with the hope being able to manage our ASA's from PRIME (and complete an LMS migration).
    When I attempt to add ASA's to prime i get the following collection errors:
    Unable to collect processor and RAM information.          Processor and RAM information.          Unexpected error. See the log file inventory.log for details.
    In the logfile I get the following XML parsing error on the MIB:
    <palError>
      <deviceId>6284310032</deviceId>
      <code>VALIDATION_ERROR</code>
      <message>Failed to validate output XML: cvc-maxInclusive-valid: Value '3484331296' is not facet-valid with respect to maxInclusive '2147483647' for type 'int'.</message>
      <result>
        <result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="/CISCO-MEMORY-POOL-MIB/xmp-im-file-system-module.xsd">
          <xmp-im-file-system-module>
            <MemoryPoolStatistics>
              <memoryPoolIndex>1</memoryPoolIndex>
              <free>4294967295</free>
              <largestFree>4294967295</largestFree>
              <used>3484331296</used>
            </MemoryPoolStatistics>
    To me it seems that the ASA returns a value that is bigger then int32 and thus causes an overflow? Any clues? Workarounds to add an ASA to Prime without checking these MIB'S?
    Regards,
    Marcel

    The X series (all with 64-bit SMP images) are not currently supported by PI 2.0. We can hope for a device update in the coming months to remedy that situation.
    If you click on the arrow next to the help icon in the top right of your PI and choose "Device Level Support" you will see:
    Cisco ASA-5500 Series Adaptive Security Appliances
    Features :
    Topology
    LLDP Neighbor Discovery
    CDP Neighbor Discovery
    Configuration
    Configuration Archive
    Software Image Management
    Monitoring
    Device Availability
    Reachability
    Inventory
    Physical
    System - Memory Pools
    Interfaces - IP
    Interfaces - Ethernet
    Device Type
    SYSOIDS
    S/W Version
    Software
    Cisco ASA-5510 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.669
    OID:1.3.6.1.4.1.9.12.3.1.3.447
    Cisco ASA-5510 Adaptive Security Appliance Security Context
    OID:1.3.6.1.4.1.9.1.773
    Cisco ASA-5520 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.670
    OID:1.3.6.1.4.1.9.12.3.1.3.448
    Cisco ASA-5520 Adaptive Security Appliance Security Context
    OID:1.3.6.1.4.1.9.1.671
    Cisco ASA-5540 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.672
    OID:1.3.6.1.4.1.9.12.3.1.3.449
    Cisco ASA-5540 Adaptive Security Appliance Security Context
    OID:1.3.6.1.4.1.9.1.673
    Cisco ASA-5560 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.12.3.1.3.454
    Cisco ASA-5550 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.753
    Cisco ASA-5550 Adaptive Security Appliance Security Context
    OID:1.3.6.1.4.1.9.1.763
    Cisco ASA-5505 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.745
    OID:1.3.6.1.4.1.9.12.3.1.3.560
    Cisco ASA-5580 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.914
    Cisco ASA-5585 Adaptive Security Appliance
    OID:1.3.6.1.4.1.9.1.1194
    OID:1.3.6.1.4.1.9.1.1195
    OID:1.3.6.1.4.1.9.1.1196
    OID:1.3.6.1.4.1.9.1.1197
    Cisco ASA-5585 Adaptive Security Appliance Security Context
    OID:1.3.6.1.4.1.9.1.1198
    OID:1.3.6.1.4.1.9.1.1199
    OID:1.3.6.1.4.1.9.1.1200
    OID:1.3.6.1.4.1.9.1.1201
    Cisco ASA-5585 Adaptive Security Appliance System Context
    OID:1.3.6.1.4.1.9.1.1202
    OID:1.3.6.1.4.1.9.1.1203
    OID:1.3.6.1.4.1.9.1.1204
    OID:1.3.6.1.4.1.9.1.1205
    Cisco ASA-5580 Adaptive Security Appliance Security Context
    OID:1.3.6.1.4.1.9.1.915
    Cisco ASA-5580 Adaptive Security Appliance System Context
    OID:1.3.6.1.4.1.9.1.916

  • Cisco Prime Infrastructure 2.0 and ASA 55xx platform problem

    Hello,
    We recently upgraded to Prime Infrastructure 2.0 with the hope being able to manage our ASA's from PRIME (and complete an LMS migration).
    When I attempt to add ASA's to prime i get the following collection errors:
    Unable to collect processor and RAM information.          Processor and RAM information.          Unexpected error. See the log file inventory.log for details.
    In the logfile I get the following XML parsing error on the MIB:
    <palError>
      <deviceId>6284310032</deviceId>
      <code>VALIDATION_ERROR</code>
      <message>Failed to validate output XML: cvc-maxInclusive-valid: Value '3484331296' is not facet-valid with respect to maxInclusive '2147483647' for type 'int'.</message>
      <result>
        <result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="/CISCO-MEMORY-POOL-MIB/xmp-im-file-system-module.xsd">
          <xmp-im-file-system-module>
            <MemoryPoolStatistics>
              <memoryPoolIndex>1</memoryPoolIndex>
              <free>4294967295</free>
              <largestFree>4294967295</largestFree>
              <used>3484331296</used>
            </MemoryPoolStatistics>
    To me it seems that the ASA returns a value that is bigger then int32 and thus causes an overflow? Any clues? Workarounds to add an ASA to Prime without checking these MIB'S?
    Regards,
    Marcel

    Hi,
    does anyone happen to know if that problem is fixed? My currently setup looks like this:
    1. Cisco Prime Infrastructure 2.1 with updated device pack.
    2. Assurance license
    3. ASA5510 which has enabled netflow. Netflow is being sent to Cisco Prime 2.1
    I do receive netflow raw data within Cisco Prime 2.1 but any graphical display of netflow data is not working. Does anybody has an idea where the problem is? Could it be that the graphical data is only displayed when sending netflow 1, netflow 5 or netflow 7?
    regards
    Maurus

  • 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

  • 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 to prime infrastructure 1.2

    Hello,
    I need to know how to do the upgrade from WCS 7.0 to Prime Infrastructure 1.2.
    I was reading and i need to upgrade to the NCS 1.1 before to go to prime infrastructure 1.2.
    I will need license to NCS 1.1 before upgrade to infraesctructure 1.2 ?
    Will i have some problem with this upgrade ?
    Can someone pass me the correct process for not have any problem with this upgrade ?
    Thank You.

    Just to add...
    Leo like to tease people with new stuff
    That is the correct path though. You will have to be first on 7.0.220.0 if your planning on exporting and importing the day from WCS to NCS 1.1. From there you will upgrade to Prime 1.2 and then you can upgrade to Prime 2.0 whenever it comes out. I would build the NCS server with the specs for Prime though.
    Just follow the configuration guide for WCS to NCS and then follow this for NCS to Prime
    https://supportforums.cisco.com/docs/DOC-26972
    Sent from Cisco Technical Support iPhone App

  • Difference between cisco prime infrastructure and cisco WCS

    Can you explain me difference between cisco prime infrastructure and cisco WCS.. I'm little bit confuse...
    Thanks..

    Hi Hasan,
    In terms of features...You can say PI is more advanced version of WCS and NCS. All the stuff possible in WCS/NCS can be done on PI as well.
    But from the architecture perspective , there are differences. If I remember correctly , WCS is based on 32 bit OS while NCS and PI based on 64 bit OS. For the same reason you cannot do inline upgrade from WCS to PI via any path and will have to change the platform/Hardware itself before moving to PI. However , inline upgrade from NCS to PI is possible if we follow the correct path.
    Regards
    Dhiresh
    **Please rate helpful posts**

  • Upgrade Prime Infrastructure v1.2.1.012 to v1.3.0.20

    Hi,
    is there any patch for upgrade from v1.2.1.012 to v1.3.0.20?
    Or I can install upgrade directly?
    St.

    But there is:
    IMPORTANT: You MUST patch your existing system prior to using this upgrade installer. See appropriate patches under Prime Infrastructure Patches.
    And in the table:
    f your existing system is...
    Download this point patch file
    Cisco Prime Network Control System 1.1.0 (1.1.0.58)
    ncs_patch-1.1.0.58-upgrade-12.tar.gz
    Cisco Prime Network Control System 1.1.1 (1.1.1.24)
    ncs_patch-1.1.1.24-upgrade-12.tar.gz
    Prime Infrastructure 1.2 (PI 1.2.0.103)
    pi_1.2.1.12_update.tar.gz
    Last row doen't match current version (1.2.1.012)
    St.

  • Error in Prime Infrastructure 2.0 after Controller upgrade

    Hello
    I've got two WiSM and Prime Infrastructure 2.0. Last week I upgraded one WiSM to 7.0.250.0, plus a third controller. That worked fine, but since then, my PI shows one of the two controllers of the second WiSM as "Unreachable". I rebooted the PI and also rebooted the controller again, to no avail.
    I tried now to update the snmp v2c credentials in PI, but receive an error.
    The error message shown when I try to update the credentials is:
    Error: Common-1: Some unexpected internal error has occurred. If the problem persists please report to the Tech Support.
    Error:Detail: errorId=6 Invalid credential name: snmp_transport.
    Any ideas?
    I can normally access the controller through its webinterface and don't see any errors that would spring to the eye.
    [edit]
    Just manualy run the Task "Controller Operational Status" and received this error:
    com.cisco.wnbu.server.common.errors.InternalException: COMMON-1
    Thanks
    Patrick

    I worked with TAC Team and the final solution was to delete all controllers and add them again. This might get fixed in a future version though.

Maybe you are looking for