WCS 7.0.164.0 - WLCs unreachable

Hi Guys,
For some reason overnight the WCS server can no longer reach the lan controllers.
They are on the same subnet and can ping both ways.
I tried deleting and re-adding but it still cannot find it.
I've tried rebooting everything and still doesnt work.
Anyone have ideas?

audit-1] Configuration Sync for device 10.60.43.253 started.
04/15/11 01:00:00.410 INFO [monitor] [audit-2] Configuration Sync for device 10.60.43.254 started.
04/15/11 01:00:14.410 ERROR [communication] [audit-1] [10.60.43.253] Unable to reach the device: 10.60.43.253/161 using SNMP version v2
04/15/11 01:00:14.410 INFO [config] [audit-1] ConfigSyncHelper auditSwitchTree:+controllerObj.getDeviceIpAddress() com.cisco.server.common.errors.DeviceUnreachableException: MEDIATION-2,10.60.43.253/161
04/15/11 01:00:14.410 ERROR [communication] [audit-2] [10.60.43.254] Unable to reach the device: 10.60.43.254/161 using SNMP version v2
04/15/11 01:00:14.410 INFO [config] [audit-2] ConfigSyncHelper auditSwitchTree:+controllerObj.getDeviceIpAddress() com.cisco.server.common.errors.DeviceUnreachableException: MEDIATION-2,10.60.43.254/161
04/15/11 01:00:14.410 ERROR [general] [audit-1] THROW
So it looks like i'll focus on SNMP?

Similar Messages

Update WCS inventory with a replacement WLC

Hi,
We are running WCS Version 6.0.181.0 and had a 5508 WLC fail that was connected to this WCS. The WLC was replaced and is running the same config and Software Version 6.0.196.0.
In WCS the old controller shows up as unreachable which you would expect, but with the new WLC online it does not see it at all. Is there somewhere that I need to change the MAC address or something for WCS to accept the new WLC?
Thanks
Tony

Thanks for that, this worked OK for me. Should you not be able to just update/audit the new one if it is called the same and has the same IP address therefore allowing you to push out the master config from WCS?
Tony

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

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

I Ask About WCS count Client not same WLC

WCS count Client not same WLC as on WLC count client = 100
on WCS count = 23-23
Wireless Control System Version 5.2.148.0
WLC 7.0.250.0
http://postimg.org/image/9boldeqd5/
http://postimg.org/image/l482i9poz/

Your WCS should have a higher (or not equal) version to your WLC.
I wouldn't even consider troubleshooting WCS problems if your WCS is running 5.X because WCS/WLC firmwares 5.X are very, very buggy.

WCS 4.1.83.0 - WLC 4.1.171. inconsistencies

Hello,
we upgraded to the above systems in the following order:
WCS to 4.1.83
WLC to 4.0.217
WLC to 4.1.171 (+bootloader update)
Now we have the following issues:
the Controllers pushed the updates towards the APs. We can confirm the 4.1.171 on the APs via the WLCs, but the WCS does always show older versions in the AP summaries, which results in problems with template rollouts (f.e. because the WLC thinks, that a 4.0.xxx AP /controller combo is not able to handle the new 4.1 templates).
When we change an option of an AP via the controller and do an audit on the WCS, THEN the WLC shows the current AP software correctly.
Is is possible to do an general audit, so we dont have to do this on every AP individually?

What happens after you refresh the config from the controllers under WCS?

WLC unreachable from WCS -

I have a WLC2000 that was reporting in to WCS but as of 2 weeks ago WCS sees it as unreachable although it is up and connectivity exists between the two?? I was planning on deleting the WLC and attempting to add it back to WCS but am curious as to if anybody had issues with similar issues?

Nah, It's just a problem that Airespace had and subsequently Cisco inherited. The WCS receives updates from the controller databases on a regularly scheduled basis. For whatever reason, everytime we get a new code version, it takes the WCS a while to learn where the controller is and what changes have been made to its database entries. You can usually manually force this by doing a manual refresh of config from the controller in the WCS commands section. If that doesn't work, you have to reboot the controller and it will come back and you can re-add it to the list of controllers IF it still shows as unreachable.

Does WCS come with the 5508 WLC?

Forum
I am providing a quote to a client for a wireless installation. I have two 5508 boxes and about 40 AP's on the quote, as well as associated SmartNet.
I was reading how the Cisco Unified Wireless Network is comprised of:
Controllers
Access Points
The Cisco Wireless Control System (WCS)
Cisco Mobility Services Engine
My questions are:
1. Does WCS come installed on the Controller? Is this something that the customer receives simply by virtue of the fact that they are purchasing the Controller? Or is this a separate piece of software with a cost?
2. What exactly is the Cisco Mobility Services Engine? What does it do that the Controller will not? How would I sell one to a customer?
Thank You
Kevin

WCS is a Windows 2003 application (so not "on the controller") that is completely separate and has to be purchased separately with different levels of licensing for different feature sets.
WCS is most useful when having several WLCs to manage and is offered when you buy a lot of stuff I think.
WCS alone brings better reporting features (graphs, pdf reports, ...) and maps to visualize everything.
MSE is a kind of "calculation appliance" that you link to your WCS to locate all clients and rogues in real-time on the map. Only that. But it's a cool enough feature :-) Without MSE you can only view one client at a time (when entering its mac address in the search field) on WCS maps.
Nicolas

Wireless Migration from WCS to NCS and MSE/WLC 7.0.230 to 7.2.110.0

Hello,
I'm in the process of ripping out all of my wireless network and putting a new one in and have a couple of questions regarding code compatibility between the NCS, WLC, and MSE.
My current infrastructure consists of Wism running 7.0.230.0 code, WCS 7.0.230.0 code, and MSE 7.0.230.0 code. I am planning on migrating my WCS over to NCS 1.1.1.24 while maintaining the 7.0.230.0 code on my WiSM and MSE. Does anyone know if this will function properly and maintain location services?
Also, I am going to be replacing my MSE (3350) 7.0.230 code with redundant MSE (3355) 7.2.110.0 code running high availability. Will I be able to import the backups/config from the 7.0.230 code onto the 7.2.110.0 new servers? Or would it be better for me to load my new servers (3355) with 7.0.230 code, import the backups, and then proceed with the upgrade to 7.2.110.0. What is the best way to migrate my CAS licenses over to the new servers?
Thanks for any suggestions.

Well here is the compatibility matrix:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
As far as the MSE, I would probably downgrade it to 7.0.230.0 and then import the backup and then upgrade. I guess you can just try it at first if you want, it won't hurt. You can always clear it and then downgrade if you want.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

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.

LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0)

I have som Aironet LAP1131AG accesspoints, that after a upgrade to WCS 5.2 (including upgrade of WLC) will not rejoin the controller.
I have attached a dump of the console. The accesspoints will upgrade the image, if they are hardreset (by holding down reset for some seconds while rebooting), but they will end up i an endless quest to join (last good message is CAPWAP changed state to CFG)...
We have 100+ accesspoints that are unaffected by the upgrade, but 2 accesspoints are giving me the same problem.
Any ideas as what to try ?

Hi
We have 2 WS-SVC-WISM-1-K9 modules. Each able to handle 300 AP's. At the moment only one of the modules are in real production. Each module contains two WLC's (WISM controllers) each capable of 150 APs. At the moment we have 32 AP on WISM-1A and 75 AP on WISM-1B. All WiSM controllers are managed from a WCS with 500 APs licensed at the moment.
Output from dir:
AP001d.e556.bf84#dir
Directory of flash:/
3 -rwx 88598 Apr 22 2009 15:00:14 +00:00 event.log
4 drwx 128 Jan 1 1970 00:02:01 +00:00 c1130-rcvk9w8-mx
9 drwx 256 Apr 22 2009 12:15:03 +00:00 c1130-k9w8-mx.124-18a.JA1
7 -rwx 5144 Apr 22 2009 15:18:20 +00:00 private-multiple-fs
8 -rwx 232 Apr 22 2009 15:18:20 +00:00 env_vars
15998976 bytes total (9431040 bytes free)
In the last days I have tried deleting env_vars, private-multiple-fs and event.log. It seemed to remove the hostname previously configured on the AP, but didn't solve the problem...

WCS v7.0.164.0 + Cisco 1142 LWAP AP's

I have deployed a number of AIR-LAP1142N-E-K9 access points at a site, but I have an issue where all access point have defaulted to Channel 1. I have set the perameters on the Lightweight AP Template correctly to allow dinamic power and channel selection. The positioning of the AP's are as per the WCS planning tool. Any help would be welcome.....

It's also possible DCA is disabled on the WLC, check it under:
802.11a > RRM > Dynamic Channel Assignment (DCA)
Also check your power:
802.11a > RRM > Tx Power Control(TPC)
Nabil

WLC unreachable

We have four WLC 5508, and a PI 2.2. We upgraded WLC one and two without any problems to 8.0.110, but when we upgraded WLC three it became unreachable in PI. Restart of PI and WLC did not fix it. I tried to remove the controller in PI but get the message: Error:Unknown Exception Occurred.
The configuration should be the same on all controllers. WLC three runs ok, it is just that I cant reach it from PI.
If I try to update credentials for WLC three in PI, i get the message: Error while updating SNMP/Telnet credentials
Any ideas??

PI is configured as trap reciever. I was using snmp v2, trying to change credentials to v3 in PI resulted in the same error: Error while updating SNMP/Telnet credentials
Trying to change snmp in controller configuration in PI resulted in the error:
Error:COMMON-1: Some unexpected internal error has occurred. If the problem persists please report to the Tech Support.
Error:Detail: errorId=8 Invalid credential name: DEVICE_PACKAGE_FINGERPRINT.

Error when adding a WLC to WCS

When adding a WLC to WCS I get this error: Failed to add device to WCS Reason:
COMMON-1: Some unexpected internal error has occured. If the problem persists please report to the Tech Support.
WCS 7.0.164.0 was upgraded from 5.2.110.0 because the WLC were running 7.0.98.0
WLC4404-100 7.0.98.0 (Already in WCS)
WLC4402-12 7.0.98.0 (Changed the ip address of the management and ap manager. Was in WCS but deleted from WCS prior to the ip address change and prior to the WCS being upgraded)
I know that the snmp strings are fine and that the WLC's both respond to snmp get commands.
The intial WCS upgrade from 5.2.110.0 to 7.0.164.0 didn't require the previous version to be uninstalled. After the upgrade and restoring the WCS from backup. I was getting the error posted above. We uninstalled WCS and re-installed WCS from scratch and still we are getting the same error. We tried restarting the WCS services and also the VM box as well and not luck. I was wondering if the WCS has the old ip and mac address of the WLC4402-12 in the database and that is why i'm getting this error.
I did delete and try different snmp community strings with no luck with WCS. Again, snmp is working since I can do snmp get from the WLC's.

Scott,
This is the issue:
com.cisco.common.persistence.transaction.TransactionException: Null value was assigned to a property of primitive type setter of com.cisco.server.managedobjects.aaa.GuestUserTemplateCG.userStatus
Could be an existing bug or a new one. I cant say unless I look into your setup.

MSE is unreachable on WCS until Java program is killed

Hi
I have a problem with my 2700 series Wireless Location Appliance. It works for about a week, then suddenly WCS shows the device as unreachable. If I kill the Java program and then perform a shutdown, it works for about a week before the same fault occurs.
Has anyone experienced this before?
Thanks
TT

JMR1: MSE becomes unreachable from periodically.
CSCtk82237
Description
Symptom:
MSE becomes unreachable from WCS periodically.
Conditions:
MSE 7.0.105.0, WCS 7.0.164.0.
CSCsy13994
Description
Symptom:
MSE shows as unreachable in WCS. The MSE service is up and running and credentials used are correct too.
Conditions:
N/A
Workaround:
Restart WCS services or reboot the WCS server.
Further Problem Description:
There is a problem with the HTTPS session being established between the WCS and the MSE which causes this issue.

WCS 7.0.164.0 - WLCs unreachable

Similar Messages

Maybe you are looking for