Upgrading WCS 7.0.164.0 to 7.0.172.0

I'm trying to upgrade my WCS from 7.0.164.0 to 7.0.172.0 but it keeps throwing me into the manual process because it detects multiple versions. Seems a previous upgrade from 6.0.132 to 7.0.164 did dot remove the 6.0.132 directory or files.
Am I safe to delete the 6.0.132 directory/files and trying again?
Thanks!

Surendra,
Thanks for the reply. By "clean upgrade" I presume you mean "manual upgrade" because the automated upgrade does not work?
Cisco Wireless Control System Configuration
Guide
Manually Upgrading WCS on Windows
Follow these steps to manually upgrade WCS on a Windows server. This type of upgrade is not recommended.
Step 1 If possible, stop all WCS user interfaces to stabilize the database.
Step 2 Back up the WCS database by following the instructions in the "Backing Up the WCS Database (for Windows)" section.
Step 3 Uninstall the WCS application by following the instructions in the "Uninstalling WCS on Windows" section.
Step 4 Install the new version of WCS by following the instructions in the "Installing WCS for Windows" section on page 2-6.
Step 5 Restore the WCS database by following the instructions in the "Restoring the WCS Database (for Windows)" section.
Going from 7.0.164.0 to 7.0.164.3 didn't work either.

Similar Messages

Import WCS 7.0.164.0 Database into WCS 7.0.172.0

We are experiencing some issues while upgrading from WCS 7.0.164 to 7.0.172. For some reason, everytime we try to import the 7.0.164 database, the 7.0.172 restore process aborts with:
Waiting for database to become idle
To Version 7.0.172.0
Invoking upgrade_general.sql
From Version 7.0.164.0
Updating Schema. This may take a while.
java.sql.SQLException: [Solid JDBC 04.50.0176] Data source rejected establishment of connection
Failed to export Hibernate schema
Hiblog.txt shows the following:
NFO 2011-07-05 10:55:03,143 [main] (TableMetadata.java:43) - indexes: [$$rrmauditdot11bconfig_primarykey_10795, rrmauditdot11bconfig_eventindex, fk254609e9ebca074c]
WARN 2011-07-05 10:55:03,175 [main] (JDBCExceptionReporter.java:77) - SQL Error: 25214, SQLState: 08003
ERROR 2011-07-05 10:55:03,175 [main] (JDBCExceptionReporter.java:78) - [Solid JDBC 04.50.0176] Connection not open
ERROR 2011-07-05 10:55:03,175 [main] (SchemaUpdate.java:165) - could not complete schema update
org.hibernate.exception.JDBCConnectionException: could not get table metadata: RrmConfig
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74)
at com.cisco.server.persistence.hibernate.dialect.SolidDialect$2.convert(Unknown Source)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:105)
at org.hibernate.cfg.Configuration.generateSchemaUpdateScript(Configuration.java:948)
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:140)
at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
at com.cisco.packaging.DBAdmin.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.zerog.lax.LAX.launch(DashoA10*..)
at com.zerog.lax.LAX.main(DashoA10*..)
Caused by: java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
at solid.jdbc.SolidError.s_Create(Unknown Source)
at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
at solid.jdbc.SolidResultSet.s_Chk(Unknown Source)
at solid.jdbc.SolidResultSet.close(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyResultSet.close(NewProxyResultSet.java:2999)
at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:101)
... 15 more
WARN 2011-07-05 10:55:03,175 [main] (NewProxyStatement.java:835) - Exception on close of inner statement.
java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
at solid.jdbc.SolidError.s_Create(Unknown Source)
at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
at solid.jdbc.SolidStatement.s_Chk(Unknown Source)
at solid.jdbc.SolidStatement.close(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyStatement.close(NewProxyStatement.java:831)
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:171)
at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
at com.cisco.packaging.DBAdmin.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.zerog.lax.LAX.launch(DashoA10*..)
at com.zerog.lax.LAX.main(DashoA10*..)
WARN 2011-07-05 10:55:03,175 [main] (NewPooledConnection.java:425) - [c3p0] A PooledConnection that has already signalled a Connection error is still in use!
WARN 2011-07-05 10:55:03,175 [main] (NewPooledConnection.java:426) - [c3p0] Another error has occurred [ java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open ] which will not be reported to listeners!
java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
at solid.jdbc.SolidError.s_Create(Unknown Source)
at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
at solid.jdbc.SolidStatement.s_Chk(Unknown Source)
at solid.jdbc.SolidStatement.close(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyStatement.close(NewProxyStatement.java:831)
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:171)
at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
at com.cisco.packaging.DBAdmin.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.zerog.lax.LAX.launch(DashoA10*..)
at com.zerog.lax.LAX.main(DashoA10*..)
ERROR 2011-07-05 10:55:03,175 [main] (SchemaUpdate.java:177) - Error closing connection
java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
at solid.jdbc.SolidError.s_Create(Unknown Source)
at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
at solid.jdbc.SolidStatement.s_Chk(Unknown Source)
at solid.jdbc.SolidStatement.close(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyStatement.close(NewProxyStatement.java:831)
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:171)
at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
at com.cisco.packaging.DBAdmin.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.zerog.lax.LAX.launch(DashoA10*..)
at com.zerog.lax.LAX.main(DashoA10*..)
WARN 2011-07-05 10:56:03,518 [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] (BasicResourcePool.java:1841) - com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@ea58e3 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:
java.sql.SQLException: [Solid JDBC 04.50.0176] Unable to connect to data source
at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
at solid.jdbc.SolidConnection.serverConnect(Unknown Source)
at solid.jdbc.SolidConnection.<init>(Unknown Source)
at solid.jdbc.SolidDriver.connect(Unknown Source)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:135)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
OS is Windows Server 2003 Enterprise, 32bit, PAE Enabled
The strange thing is, we had a case open and the TAC-Engineer was actually able to import the database, since it looked like a issue with our virtual machine we agreed to close the case and continue testing on another server. However after moving to a proper server the problem still exists.
Also it doesnt matter if we try a direct upgrade install with automated migration or a fresh install with manual db import, its always the same error during the hibernate export.
I think i will reopen the case later but maybe there is a more simple solution to that problem?
Thanks a lot
Kind regards
Christian

Hi Jorge,
It looks like such a level of granularity may not be achievable yet.
Should you need such a feature to be evaluated for potentially being included in future software releases, I would recommend to contact your local Cisco account team.
They should be able to follow up and submit a product enhancement request (PER).
Business units will evaluate PERs and, if feasible for the market, they may consider implementing such an enhancement in future versions of the SW/HW.
Regards,
Fede

WCS 7.0.164.0 Report by vendor (device type)

WCS 7.0.164.0
I have been asked to produce a client’s report that shows all different vendors (devices type). We have about 10000 users in our system on about 3000 APs (light version) I created a client summary report but encountered some limitations:
If I select any time period over 6 hours, I get the message “The report you are trying to generate contains more than the supported number of records (10000). Change the report criteria to generate a report with fewer records”
If I select a time period of 6 hours or less, I get the report including vendor statistics. Is there any way to differentiate within the vendors by device type? For example instead of the vendor apple, get apple-iPhone, apple-iTouch, apple-laptop, etc.
I would like the ability to create my own reports, by I don’t think it is possible on the Version I’m running. All reports can be customized up to a point, but you still get information you might not care for.
Thanks for any information to overcome these issues.
Jorge Jiles.

Hi Jorge,
It looks like such a level of granularity may not be achievable yet.
Should you need such a feature to be evaluated for potentially being included in future software releases, I would recommend to contact your local Cisco account team.
They should be able to follow up and submit a product enhancement request (PER).
Business units will evaluate PERs and, if feasible for the market, they may consider implementing such an enhancement in future versions of the SW/HW.
Regards,
Fede

How to upgrade WCS Plus 500 to 700?

To upgrade WCS Plus 500 lic to support 200 more APs, which one is the correct choice?
1. Add WCS Plus 100 lic x 2; or
2. Add WCS Enterprise 1000 lic
Refer to ordering guide
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd804b4646.html
Cisco WCS is licensed as either a single server or enterprise deployment.
Single Server License Overview
• Licenses: WCS-STANDARD-K9, WCS-PLUS-UPG-K9, and WCS-WLSE-UPG-K9
• License increments: 50, 100, 500 (Up to 1500 for WLSE-to-WCS conversion only)
• Single server deployment
• Suitable for customers deploying up to 500 (Up to 1500 for WLSE-to-WCS conversion) Cisco Aironet lightweight access points
• One license file per Product Authorization Key (PAK) certificate
• Available in WCS Base and WCS PLUS configurations
Enterprise Server License (Multiple Servers) Overview (release 4.1 or later)
• License: WCS-ENT-PLUS-K9
• License increments: 1000, 2500, 10000, 50000
• Single or multiple server deployment (Cisco WCS Navigator included in 10000, and 50000 licenses)
• Suitable for customers deploying 500 or more Cisco Aironet lightweight access points
• Multiple license files linked to a single PAK certificate
• Server decrements available number of access points as licenses are allocated within the network
BUT
All Cisco WCS licenses of the same option (Base or PLUS) are additive. Cisco WCS licenses can be combined to support an incremental number of access points (such as 300, 700, 900) beyond the distinct license increments (such as 50, 100, 500) offered.
Example 1: To purchase a new single server license for 800 access points
Purchase: WCS-STANDARD-K9, (1) WCS-APBASE-500, and (3) WCS-APBASE-100
contradiction in the doc.

Existing
1
x
WCS-PLUS-500
Cisco WCS with PLUS License for 500 APs, Windows/Linux
Target upgrade to monitor
700 APs

Upgrading WCS 7 to Cisco Prime (CPI) 2

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

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

Upgrading WCS to Prime

I'm in the process of upgrading a customer's WCS server to Prime. I know before I can upgrade the WCS server to Prime. I must first upgrade the WCS sever to NCS. My problem is the customer's WCS server is running software version 7.0.230 and I need to upgrade it to 7.0.240 before I can extract the WSC database. My question is, if I upgrade the WCS server from 7.0.230 to 7.0.240 will that cause the customer's Wireless Lan Controllers that are being managed by WLC server to also upgrade?

Maurice, I had a devil of a time upgrading WCS to NCS to Prime.
Long story short, I found the time taken on a very unsuccessful WCS->NCS->Prime migration was 4-8 times longer than the time it took to just install Prime, add the WLCs, and manually rebuild the maps.
YMMV.
PS, Cisco Prime LMS is probably replacing their wired management software (often LMS, Cisco Works+ RME, etc). I believe every best-practice guide I've seen from Cisco says to have one Prime for wireless, and one Prime for wired... even though Prime looks like it could handle both.

Upgrading WCS to v7.0

I plan on upgrading WCS from version 6.0.181.0 to 7.0230.0
Is there any reason not to or concerns?

As Steve pointed out you should be fine. Here is a WLC and WCS software matrix if you want that warm and fuzzy ..
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html

Upgrade WCS to Prime

Hi Can anyone please advise if a current working Cisco WCS systems can be upgraded to Cisco Prime. Also is there a requirment to upgrade the license or is it just a case of upgrading the software.

Yes, you can upgrade WCS 7.x to Prime Infrastructure. I'm not sure if you can go straight to 1.2 but definitely you can go WCS 7 - NCS 1.1 (PI 1.1) - PI 1.2. See this guide.
A new license is required. See this reference (Table 7) for details.

Upgrade WCS 7.0 to PI 1.2 via NCS 1.1

Hello all,
we have started to do the upgrade from WCS 7.0 to PI12. In order to do that we first need to upgrade to NCS 1.1. We have ordered the following from Cisco:
R-W-PI12-M-K9
WCS 7.0 to Cisco Prime   Infrastructure 1.2 Migration
N/A
14 days
No
N/A
1
1.995,00
1.995,00
0
1.995,00
R-PI12-BASE-K9
Prime Infrastructure 1.2 Base   License and Software
N/A
14 days
Yes
N/A
1
0,00
0,00
0
0,00
L-PI12-LF-500-LIC
Prime Infrastructure 1.2 -   Lifecycle - 500 Device Lic PAK
N/A
14 days
Yes
N/A
1
0,00
0,00
0
0,00
L-PILMS42-500-M
Prime Infrastructure LMS 4.2 -   500 Device Upgrade Lic
N/A
14 days
Yes
N/A
1
0,00
0,00
0
0,00
L-PI12-LF-100-LIC
Prime Infrastructure 1.2 -   Lifecycle - 100 Device Lic PAK
N/A
14 days
Yes
N/A
3
0,00
0,00
0
0,00
L-PILMS42-100-M
Prime Infrastructure LMS 4.2 -   100 Device Upgrade Lic
N/A
14 days
Yes
N/A
3
0,00
0,00
0
0,00
L-W-PI12-500-M
WCS to Prime Infrastructure 1.2   Migration 500 Device
N/A
14 days
No
N/A
1
0,00
0,00
0
0,00
L-W-PI12-100-M
WCS to Prime Infrastructure 1.2   Migration 100 Device
N/A
14 days
No
N/A
3
0,00
0,00
0
0,00
I have done the upload of the XML File from our WCS 7.0 installation to get the License File. But on the NCS 1.1 installation the following License is needed first (Cisco Prime Network Control System 1.1 Config Guide):
NoteBefore adding the licenses that are migrated from your WCS installation, apply the L-WCS-NCS1-M-K9 license. The licenses migrated from WCS are generated as “ADD” licenses, and you cannot apply them unless you apply the L-WCS-NCS1-M-K9 license.
L-WCS-NCS1-M-K9 is the Product Number to do the upgrade from WCS 7.0 to NCS 1.0, R-WCS-PI11-M-K9 is the product number to dothe upgrade from WCS 7.0 to NCS/PI 1.1.
If I try to install just the License File I get from Cisco using the XML file from our WCS 7.0 installation, I get the error "Unable to add any license without an NCS (L-NCS-1.0-K9) license.".
But how do a get this license if I ordered R-W-PI12-M-K9 (WCS 7.0 to PI1.2 Upgrade License)? What is the step to get the right License?
Many thanks in advance for any help on that issue.
Best regards,
Hans

Hello Joe,
no. The information in the deployment Guide (the link i proveded before) is wrong.
You still need to follow the upgrade path WCS 7.0 -> NCS 1.1 (here you have to use for example 1.1.1.24, because 1.1.2.12 cannot be upgraded to PI 1.2), then you can upgrade NCS 1.1 to PI 1.2 (if you upgraded the WCS to NCS 1.1.1.24 you need to install a patch ncs_patch-1.1.1.24-upgrade-12.gz, for other 1.1 releases you need a different patch).
The major problem was the licensing. Because with the order of the Upgrade Licenses from WCS 7.0 to PI 1.2 I got "normal licenses", for PI 1.2, a Base License and Lifecycle Licenses (the number of Lifecycle Licenses matches the number from the order).
Because we ordered the WCS 7.0 to PI 1.2 Upgrade Licenses I also ordered the NCS Appliance with the PI 1.2 (before I thought a direct upgrade from WCS 7.0 to PI 1.2 should be possibel, why not, if you can order the licenses with the description Upgrade License WCS 7.0 to PI 1.2 :-)). So I had to downgrade the NCS Appliance to NCS 1.1. After the downgrade the NCS Appliance came up without any licenses. So the major porblem was that I could not use the PI 1.2 licenses (they are not installable on NCS 1.1). So I got a demo/temporary license from Cisco for NCS 1.1 to do just the migration. After the final upgrade to PI 1.2 I installed the base and the lifecycle licenses and now everything is fine.
Best regards,
Hans

Upgrading WCS with RH5.x - do I have the correct files

Hi All,
My supplier seems to be just as ignorant as me regarding the following:
I have a disc labelled 'WCS-WLSEU-RH5-Upgrade.iso' - will I be able to upgrade my WCS' OS (running on RH4 on a WLSE appliance) with this disc, or is it actually for converting a WLSE to WCS (and our supplier has given me the wrong thing- which is what I am afraid of)?
Many Thanks for any help you can give,
Scott

Hi
The image that you have will upgrade the operating system to red hat 5.0. This version is a requeriment if you want to use WCS 5.0 and higher.
You have to burn the image in a CD and boot with this CD in order to perform the upgrade.
Where do you find this image, I have been searching it in the cisco web site but i can`t find it.
Would you mind telling me , where is located this iso file?
Thanks in advanced

Upgrading WCS from 4.2.62.11 to ?

Hello All,
I recently purchased 6 1142 AP's and added them to my controller, well since these are not LWAP but instead CAPWAP AP's they were not supported by my WLC with code version 4.2 (not the end of the world) so I upgraded the WLC to code 6.0.182 but had to sacrifice managing it from my WCS.
Now I would like to upgrade my WCS to support managing this WLC again and potentially upgrading my remaining WLC's, the thing is I would like to upgrade to the latest WCS version 6.0.132 but need some input as to the ease of upgading, and/or any potential problems that might surface, or if anyone is currently experiencing any issues using this WCS code. Will 6.0 be the best bet or is it sufficient to step up to 5.2? Are you satisfied with this upgrade? How many WLC and AP's are you managing? Is there anything I need to consider that isnt written in the Cisco documentation?
Any input would be greatly appreciated.

You do need WCS 6.0.132.0 to manage your 6.0.182.0 WLC.
To upgrade, its easy, just make a backup of your db, run the installer of 6.0.132.0 and you will be all set. There are not really issues in the upgrade and this should go smooth.
WCS 5.2 will not support your WLC running 6.0
WCS 6.0.132.0 release note:
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html

Upgrade WCS

What are the requirements to upgrade the WCS 4.0 to 4.2?

Hi Ricardo,
Here is the related info;
Upgrading to a New Software Release
The Cisco WCS release must be the same or more recent than the controller software release. Upgrade the Cisco WCS first to prevent any unexpected problems.
Note If you upgrade to a Cisco WCS software release later than 4.0.87.0 from a release prior to 4.0.87.0, the users, user groups, tasks, and user passwords do not migrate. Upgrading to 4.0.87.0 before upgrading to a later release migrates the users, user groups, tasks, and user passwords.
Cisco WCS supports database upgrades only from the following official Cisco WCS releases:
â¢4.0.66.0
â¢4.0.81.0
â¢4.0.87.0
â¢4.0.96.0
â¢4.0.97.0
â¢4.1.83.0
â¢4.1.91.0
â¢4.2.62.0
From this good doc;
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCSRN4_2_62_11.html
Hope this helps!
Rob

Upgrade WCS 5.1.64 to 6.0.196 Questions

Hi,
Im currently testing the WCS upgrade from 5.1.64 to 6.0.196 and I have a couple of questions that I cant find the answers to.
1. Will I require a new license to move from 5 to 6 or even to 7?
2. Will I need to reinstall the license files I have for the 150+ AP's I have or will all licenses be handled as part of the automated upgrade process?
Cheers
Dylan

Hi,
The current licenses will work on the upgraded version.
Simply follow the upgrade procedure and the licneses will be ok on the new version.
HTH,
Tiago
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

WLC code upgrade, WCS, ap_3600

i'm going to upgrade a 5508 wlc code from
7.0.116.0
to
7.1.91.0
to add 3600 series access points having it all manageable via WCS ver 7.0.230.0
it seems to be possible, as it is explained in the compatibility matrix found on
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
now I have to download the file to the controller...
AIR-CT5500-K9-SPECIAL-7-1-91-0.aes
(direct update possible)
before doing that I'd like to know if I will loose my configuration on the controller
i'm concerned about that because the release document is not clear:
- We highly recommend that you back up your controller's configuration files prior to upgrading the controller software. Otherwise, you must manually reconfigure the controller.
- For busy networks, controllers on high utilization, or small controller platforms it is advisable to disable the 802.11a/b/g networks as a precautionary measure.
- Step 5 Disable any WLANs on the controller.
- Step 19 Re-enable the WLANs......
- Step 22 If desired, reload your latest configuration file to the controller. (reload config after reenabling wlans????? why???)
so will I loose my configuration?
what is Field Upgrade Software? should i use that instead?
another controller another question .....: a cisco wlc 2100
found 2 update files
AIR-WLC2100-K9-7-0-230-0-ER.aes
AIR-WLC2100-K9-7-0-230-0.aes
why 2 update files this time? what file to update first?
thank you in advance for your answers

The 5508 has two files when you go to 7.2, which I would for the 3600. You'll also want to download and install the FUS image.
the 'legacy' WLC, like the 2100, have the .aes which is the OS for the WLC. The -ER is an Emergency Recovery image, it's waht you get when you break the boot cycle.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Multible installations of WCS detected - when trying to upgrade WCS

Does anyone have an idea of how to work around this problem ?
When i try to upgrade a WCS (from 7.0.172 to 7.0.230) it tells me that i cannot upgrade because it has detected multible installations of WCS.
When i search through "add / remove programs" and "program files" there are no other installations.
How does the WCS installations detect other installations and how do i work around this ?

Thank you for your response.
I have searched all of the drive (this server only has C:\) and i still cannot find anything.
I have started to search through the registration datatbase, but no luck so far.
I have even tried to uninstall the 7.0.172 i was upgrading from.
It even gives the same error message when trying to reinstall 7.0.172.
/Thomas

Upgrading WCS 7.0.164.0 to 7.0.172.0

Similar Messages

Maybe you are looking for