topic Re: WCS 4.2.62.0 error in Wireless

WCS 4.2.62.0 error

jkennedy — Sat, 03 Jul 2021 22:00:56 GMT

I just upgraded to 4.2.62.0 and I have found one strange error. I go to configure >access points> click on an access point to configure and I get this message.

Error(s): You must correct the follow error(s) before proceeding:

Error: Object "Switch" does not exist.

Has anyone else seen this?

Re: WCS 4.2.62.0 error

pmccubbin — Wed, 28 Nov 2007 21:02:58 GMT

Hi Jeremy,

I found this in the Release Notes for WCS 4.2:

CSCsk51302-When you click on Client Troubleshooting in Monitor > Clients, an "object switch does not exist" error displays.

Workaround: None at this time.

Are you able to configure the AP via the WLC?

What version of WLC software are you running?

Hope this helps.

Paul

Re: WCS 4.2.62.0 error

jkennedy — Wed, 28 Nov 2007 21:08:07 GMT

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.

Re: WCS 4.2.62.0 error

jkennedy — Wed, 28 Nov 2007 23:08:05 GMT

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.

Re: WCS 4.2.62.0 error

pmccubbin — Thu, 29 Nov 2007 00:09:27 GMT

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

Re: WCS 4.2.62.0 error

johnruffing — Mon, 24 Dec 2007 18:19:44 GMT

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)