Radios policy on WLAN ignored on WLC

[tdennehy]

The scenario:

WISM2 running 7.0.220.0

Healthcare = can't just take it offline or upgrade on a whim.

Guest Wi-Fi profile set to 802.11g-only

SSH into controller.  Here's from the CLI:  wlan radio 3 802.11g-only

So... it is set to 802.11g only, right?

Nope.  Not only can I see guest clients on 802.11a on the controller, but I can go there with AirMagnet WiFi Analzer and see the guest WLAN being broadcast on 802.11a.  I can set up my laptop to only use 5GHz radio chain and sure enough, I can get on the guest wireless network.

The impact from this is that we run our voice on 5GHz, along with other production wireless.  Our guest network is half of our clients, and we cannot have them on our 5GHz spectrum.

I thought we were running into CSCty61970, but we're running 7.0.220.0

Does anyone have any good news for me, besides "upgrade to 7.x.xxx.x?

[Leo Laohoo]

Could be a bug.  

Problem is that with 7.0.X you can't force to enable Radio Policy Group because it aint supported.  This would've been your work-around.

[tdennehy]

Yeah.  Agreed.  I only wish someone at Cisco would acknowledge their is a problem with this code and provide a fix for it.  You can't just take down a 24x7 environment.

Both the GUI and CLI show the radio policy set to 802.11g, however I know it is NOT.  I have solid proof with packet captures and can even set a laptop to a-only and it will jump right on.  Yes, that's a problem.

I saw a bug 16970, but it doesn't show the same versions.  Almost 500 access points on a controller in a 24x7 environment, and now the guest clients are hitting the 5 GHz.

There needs to be a fix.

[Scott Fella]

Well, I have never heard of that issue before.  I can tell you that TAC would tell you to upgrade to the latest v7.0.x for the fix.  What you can always do is move your AP's to one of the controllers and upload all controllers and use the pre-download, if your AP's are supported and then reboot =the controller that has no AP's.  Then you can move AP's to that controller to limit the downtime.  If your AP's don't support the pre-download, then you are stuck.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-0/configuration/guide/c70/c70mfw.html#wp1132291

Please rate helpful post and Cisco Support Community will donate to Kiva

Scotty

[Abhishek Abhishek]

Please update to the latest version and check.As it might be a bug on the previous versions.

[jmeachum]

I would verify that it is set to G only on all of your controllers and also ensure that Client Band Select is not enabled on the WLAN.

I hope this helps.

John

[anthony.king]

I had a similar problem a while back with 7.2 code.  As I recall, I had my APs in groups and, at some point, I upgraded software on the controller.  After the upgrade, the radio policies were ignored.  I had to remove the APs from their groups and put them back in again and the policy worked again.  The only problem with that process is that it is just as disruptive as upgrading.

[Abha Jha]

Seems like you are getting effected with bug like

CSCud37443    Clients connect in "b/g" even when ssid radio policy set explicitly "a"

upgrade is the only solution.

You may also try below as workaround :-

++Reconfiguring the SSID

 
++ Also removing the WLAN from the AP groups and re-inserting