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

Similar Messages

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

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

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

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

Upgrading from Prime 1.2 to 1.3 - What about WLC version?

If I upgrade to prime v1.3, from v1.2, am I required to upgrade my WLC controllers to v7.4, or will my current version (v7.2) work fine?
Thanks.

No upgrade to your WLCs is required. Any v7.0 or later should be fine. See the Release Notes here for details.

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

SNMP on CAPWAP via WCS or Cisco Prime

We are interested in adding SNMP settings to all of our CAPWAP wireless access points. There is no way to do this via any of our controllers or WCS. We are soon to upgrade to Cisco Prime.
I am able to log in via telnet to a 3502 and manually enter SNMP commands, however I can't save the running config to NVRAM. I can save the running config to flash, but can't change the config register to look at flash for the config on startup.
Is there a way to configure and save SNMP parameters on CAPWAP wireless access points?

The referenced document states that SNMP management is available. However, The SNMP settings on a controller (5508 as an example) allows for traps on the controller itself and not on the CAPWAPs.
We have an inventory management system that we want to import our CAPWAPs. There are over 2500 so manually imputing the CAPWAPs can be a tedious task. The management system uses SNMP to discover said info. All of the controllers are already cataloged.

Upgrade to Prime 2.0 from LMS 3.2.1

Hello all, and thanks in advance for any help you can offer. Is there an upgrade path from LMS 3.2.1 to Prime Infra 2.0? Or given 2.1 is now available perhaps to 2.1?
My plan of attack at the moment is to download the OVA for the Small deployment, and build out the DB from scratch. But we do have a significant number of devices so I was wondering if some sort of DB import was possible. It appears that I would have to upgrade our current LMS to 4.2 first to do this though, and that is more hassle than its worth if that is in fact the case.
The other question I had is around licensing. We currently have LMS and NCS running in our environment. How can I combine the licensing from each so I can get the same levels on Prime Infra? Both NCS and LMS are under software support if that helps at all.
Please advise, any help would be greatly appreciated.
Jeff

You can't do a direct db import but you can use the dcrcli utility in LMS 3.2 to export a csv file of your devices and credentials.
You can then manipulate it using Excel or such to match the required format in PI 2.x. (That's basically what's done for you if you go the the trouble of upgrading to LMS 4.2 and using the export utility there.)
There are upgrade SKUs available for NCS to PI. Your reseller or Cisco partner can use the Cisco Prime "BOM Builder" (ordering guide available (only to partners) in the partner community) to determine the correct part number to order.

Error to do upgrade with Prime Collaboration Deployment

Hi all,
We need do a upgrade from CUCM 8.0 to 10.0
We are migratin with the Prime Collaboration Deployment, but when we add the Esxi host, an error appear.
"Failed to mount Cisco Prime Collaboration Deployments export as NFS store to the ESXi Host"
The UCS is a UCS 240.
We can discover the cluster old, but don´t cant add the Esxi host.
We deploy the new VM for the new CUCM 10.0
Please, I need your help.
Thanks
Guillermo

Most likely you don't have the right ESXi license for this, you need at least FND for PCD
Page 11
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/ucmap/10_0_1/CUCM_BK_U9C58CB1_00_ucmap-administration-guide.pdf
If you don't meet the ESXi license requirements, nothing to do here, either buy the necessary license, or don't use PCD.

WCS Upgrade to 7.0.172.0 - random AP impersonation alerts...

I upgraded our WCS over the weekend to the new 7.0.172.0 release. Daily now I am getting one or two "ap impersonation" alerts which I wasn't before. These are coming from existing clients that have been on the network for quite some time.
Has anyone else seen this?

Same here - it would be awesome if somebody ran across this that had a definitive answer. There has to be more people with the issue. Right now I have 200 "Critical Alarms" - mostly the AP Impersonation alarms.
It really is an annoyance, especially since with that many, it's easy to overlook the important ones. I don't remember when this started happening, but every upgrade I install I keep hoping it will get fixed.
I guess if I ever get to a point where I feel like wasting more time on it, I'll log another case and see what happens with it.

WLSE to WCS upgrade path

Hi,
Could anybody tell me if they are aware of an upgrade path from WLSE to WCS using existing WLSE hardware? Can anybody point out the main benefits/features moving to WCS from WLSE?
Many thanks
SJ

Hi Scott,
Just the 1130-19 or 1133 are supported;
The new Cisco WCS SKU family, WCS-WLSE-UPG-K9, is now available for CiscoWorks WLSE customers that wish to migrate from CiscoWorks WLSE (Models 1130-19 or 1133) to Cisco WCS. These new SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
All CiscoWorks WLSE conversion SKUs ship with two special conversion CDs. These CDs check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
This SKU family supports only ***CiscoWorks WLSE hardware models 1130-19 and 1133. To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. ***Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Note: CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Model 1105) are not supported with CiscoWorks WLSE conversion SKUs. Do not install the CiscoWorks WLSE CDs on the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and it will not work.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Autonomous access points are not supported by a converted CiscoWorks WLSE.
Customers migrating their CiscoWorks WLSE to Cisco WCS do not need to buy a copy of RedHat Linux ES v. 4.0 software. A copy of RedHat Linux ES v. 4.0 software is included with the CiscoWorks WLSE migration CDs. (RedHat Linux AS v. 4.0 is not supported by a converted CiscoWorks WLSE.)
From this good doc;
http://www.cisco.com/en/US/products/sw/cscowork/ps3915/prod_bulletin0900aecd804b4635.html
Hope this helps!
Rob

Installing WCS - upgrade path

Hello, I have WCS with location version 3.0.101.0 on CD, and want to know the best path to take regarding installing and upgrading to work with my controllers. I have two WiSMs with versions 3.2.78.4 and 4.0.179.11 with about 350 access points. I know I need to upgrade the controller verisons to be the same. Should I upgrade to WCS 4.0.87.0? Do I need to upgrade in steps, or go for the latest version right off. I want to upgrade WCS before adding any controllers.
Thanks

We upgraded our WLCs to 4.0.179.8 prior to installing the WCS (installed from scratch 4.0.81.0) and had good success.
The release notes for 4.x discussed a problem if you update the WLC to 4.x while the LWAPs are connected. I remember something about the APs being unable to download the new firmware successfully which sounds like you could end up with a real mess on your hands if the APs lock up in that state.
From page 6 of the installation notes: 6 "Connecting 1100 and 1300 Series Access Points: You must install software release 4.0.179.8 on the controller before connecting 1100 and 1300 series access points to the controller."
Here is the link to the installation notes:
http://www.cisco.com/cgi-bin/Software/Tablebuild/doftp.pl?ftpfile=cisco/crypto/3DES/wireless/aironet/WLAN/4400/WLC-4.0.179.11-ReleaseNotes.pdf&app=Tablebuild&status=showC2A
In terms of AP licensing, we ran into an issue where there were no AP licenses for the WCS. However, since this was a new install of WCS 4.0, and you are performing an upgrade, your experience might be better than ours was. If you run into AP licensing issues with WCS 4.0, you may want to reference the following forum thread:
(forum user, ethiel, ended up with better information than TAC on this particular problem):
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddc79a8
Finally, you may want to double check the firmware rev levels of your existing access points. Hopefully, this will not apply to you, but since you said you are running 3.x on one of your WiSMs...
Message Type : Field Notice
Title: Cisco Field Notice: FN - 62474 - LWAPP 1231 Fails to Upgrade to 4.0.155.0 with 4402 Image
URL:
http://www.cisco.com/en/US/customer/products/hw/wireless/ps430/products_field_notice09186a00806e3ac7.shtml
Posted: July 14, 2006
Summary: When a 1200, 1130 or 1240-series Access Point, with an LWAPP image installed that is prior to 12.3(11)JX, attempts to connect to a Wireless LAN Controller running 4.0.155.0 software, the Access Point may be unable to complete downloading its updated
software.
Hope this helps
- John

WLSE - WCS upgrade license question

Hello,
We need to upgrade our WLSE to WCS but our sales people bought the wrong license (WCS-Standard-K9) Is it possible to upgrade the WLSE to WCS with this license and just get the conversion CDs needed from you ?

Hi Gudmundur,
This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
[email protected]
Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Please see Appendix C for information about receiving support for existing SMARTnetÂ® (hardware support) contracts for CiscoWorks WLSE.
Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
Base or Location
Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
PAK Certificate, Instructions and CD
Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
Hope this helps!
Hi Gudmundur,
This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
[email protected]
Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Please see Appendix C for information about receiving support for existing SMARTnetÂ® (hardware support) contracts for CiscoWorks WLSE.
Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
Base or Location
Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
PAK Certificate, Instructions and CD
Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
Hope this helps!

WLC/WCS upgrade questions

Hi, we have 2 4402 controllers running with system software 4.2.130.0. The WCS is running 4.2.110.0.
I would like to upgrade but are a bit confused about all the different versions.
Is it recomended that I upgrade directly to the latest 6.0.182(WCS)/132(WLC) ?
And how do I upgrade ? the controllers first and then the WCS ?
Regards
Johann Folkestad

If you are considering upgrading to 6.0, here is the section of the release notes for the WCS that concerns that:
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html#wp44448
As for the WLC, here is that section:
http://www.cisco.com/en/US/partner/docs/wireless/controller/release/notes/crn601820.html#wp472449
As already stated, be sure to read the release notes to find which version is best for you.
List of Release Notes for WCS Versions:
http://www.cisco.com/en/US/products/ps6305/prod_release_notes_list.html
List of Release Notes for WLC Versions:
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html

WCS upgrade question

Hi-
I have recently installed WCS 4.0.96 on Windows 2003. Foundstone is detecting an Apache/TOmcat vulnerability.
I saw on Cisco's website that the latest versions are 4.0.97, and 4.1.91.
Can I upgrade to 4.1.91 by downloading the file on the website? Does it work with the license I have for 4.0.96?
Thanks!

Have just upgraded my own wcs, and licensing remained due to the backup made before upgrade/reinstall and restore afterwards.
Notice that the upgrade is a little complicated.
1. backup your wcs
2. uninstall your wcs
3. install the new version
4. restore your backup (have patience) this wont work if your server has less than 2 Gb of memory.
reload the server, and voila your wcs is back online
/Henrik

WCS upgrade and HTTP port open

Hello All,
I am trying to upgrade my Wundows based WCS 4.2.97.0 to 5.2.130.0.
During the upgrade it tells me that port 8 (http)is needed by WCS and being used by another application. I have tried to find out which application is using that port so that I either stop the app or service and failed.
Would anyone kow a quick way to discover/disable the app on a Win 2003 server/
thanks a lot
Bo

Hi ericgarnel,
I am not running IIS on the server. I removed the WCS 4.2.97.0 and rebooted the server. I still get the same port hhtp (port 80) is being used by another application.
thanks
Bo

WCS upgrade to Prime 1.2

Similar Messages

Maybe you are looking for