Yes I am able to configure the ap via WLC. I'm running 4.2.61.0 on the controller. I've noticed that my ap groups disappeared on my controllers after upgrade. They are still on the WCS controller template though. I'm going to try and recreate them and see if that is what could be causing this problem. Any help would be very appreciated.

Ok I found an older thread about 4.2.61.0 code and issued the "refresh from controller" command from the WCS. This fixed my problem.

Hi Jeremy,

Thanks for letting the forum know about how you resolved the problem. I give it a "5" and hope you stay involved here.

Best,

Paul

For what it's worth, discussions with Cisco TAC have indicated that after you perform a code upgrade, you need to perform a "Refresh from Controllers" from the drop down on the WCS screen (under Configure->Controllers) for each of the controllers managed by the WCS.

We ran into this snag ourselves when the WCS showed our access points at a previous code revision level. Of course, this condition cannot be possible since the LWAPs must ALWAYS be at the same rev as the controller.

After a discussion through Cisco TAC with the WNBU DEs (the guys who write the code), they indicated that in order for the WCS to be in synch with the controllers after a code upgrade, a "Refresh config from Controllers" command must be issued.

When asked why the WCS does not automatically do this, it was stated that we should talk to our sales team about a feature enhancement.

(Apparently, the developers feel that having the WCS and controllers in synch is an "enhancement")

In any case, after an upgrade, manually forcing the WCS to refresh the configuration from the controllers is a pretty good idea.

- John

(Please remember to rate helpful posts)