WCS Refresh Config from Controller Fails

Unanswered Question
Sep 5th, 2007

Have been able to refresh config from controller successfully in the past, but now it only works on 1 of 4 controllers. Receive error "Failed (see logs)". Any idea why this would fail, and/or where I can find these logs? All controllers are reachable.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
ericgarnel Thu, 09/06/2007 - 05:17

What do the logs say?

Also, have there been any changes to the network between WCS and the controllers? Has the WCS server OS been updated recently? and which OS, windows or linux?

If anything, retype in the snmp values and try again

becca1jane Thu, 09/06/2007 - 15:49

Finally found the error in the logs - failure is occurring when setting attribute bridging shared secret. In WCS I went to go look at at bridging on one of the controllers I'm having a problem with and I can't even access the page - receive error "Unknown Exception Occurred. If the problem persists please send logs to the Tech Support."

DANIEL FERREIRA Fri, 09/07/2007 - 03:16

I have the same issue. I added two new controllers to the network and the refresh was fine. After i have had the maps and assigned the access points to the maps can not refresh config from controller and receive the same error "Failed (see logs)"

becca1jane Fri, 09/07/2007 - 09:57


Have you had a chance to look at the logs to see where the error is coming from?

DANIEL FERREIRA Mon, 09/10/2007 - 05:41

Now everything works fine. The problem was the name of the interface that has space between names ("xxx ? xxx?). I have changed the notation for a new one without spaces (xxx-xxx) and now it?s ok. The logs says this:"could not insert:[com.cisco.server.managedobjects.bridge.InterfaceConfig]".

For what it's worth, it is generally recommended that the WCS be at a MORE recent or same revision level (in terms of date, not version numbering, per se) as the controllers.

Have you upgraded the controllers prior to the WCS? It is my understanding that upgrading in the wrong order (i.e.: Upgrading the WLC/WiSM before the WCS is upgraded) might cause problems.

Just a thought.

- John

Andrew Schulz Fri, 02/22/2013 - 13:21

I am having this problem as well. I recently upgraded my WLC from 7.2 to now I get this error. I've downloaded the logs, but where in the H do you look to find out what is causing this?

Andrew Schulz Mon, 02/25/2013 - 11:03

So, are you telling me that WCS no longer works with this version of the WLC software and that I need to purchase and install Prime Infrastructure? Or is there an upgrade that needs to be applied to WCS?

Scott Fella Mon, 02/25/2013 - 12:56

Take a look at the compatibility matrix. That shows you what is supported and what's not. If your running 7.3 in the WLC then you need Prime Infrastructure 1.2 at least.

Sent from Cisco Technical Support iPhone App

Andrew Schulz Mon, 02/25/2013 - 12:58

Yes, I did thanks. Not super clear but I also found the mirgration from WCS to NCS which made it a little more clear. I got it figured out now though. Thanks for the support.

andy.winford Thu, 04/30/2015 - 19:57

Scott, I can't find any information on this other than this particular thread.  I upgrade 1.4 to 2.2.  Controller is on 7.6.110.   I get this error.   Check the logs is sorta frustrating because I'm not sure which log this would be under and their are literally dozens.   Any ideas?   Is there something missing on the controller side I need to change?


This Discussion



Trending Topics - Security & Network