WLC Version 7.0.250.0 Problems

Question

I just wanted to warn that I have had serious problems with version 7.0.250.0 and have had to roll back to 7.0.240.0 on all controllers.
Initial testing on a WiSM v1 seemed ok (an upgrade fron 7.0.235.3). Still have one WISM controller working fine on this version with no issues at all.
Roll out to other WISM v1, 5508, 2500 and 3750G integrated controllers saw almost complete unusable wireless connections from almost all Windows clients (Intel 3945 6100 6200 6300 nics) attached to a WPA2 AES network with 802.1x + CCKM. Mixture of APs but mostly 1142N and 3502. MFP disabled due to previous intel client issues.
Main crux of the problems were drops in connection and when connected slowed to a complete crawl. Data transfer speeds were less than a few kb/s when they were associated at m15 speed!. I also had one controller put all a/n access points on the same channel when DFS was enabled.
All metrics seemed fine on the client RSSI/SNR etc could not see anything obvious at all.
A roll back immediately solved all problems.I was unable to log a TAC case at the time to investigate due to the severity of the issue.

Answer 1

It seems we also have this issue with 3502 AP and WiSM1. The previously smooth working 14.x (year 2011)  drivers from Intel with an Intel 6305 card don't anymore correctly work now. Controller doesn't show much. If I "troubleshoot" the client in Prime and collect the logfiles, then I get this all the time:
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 0, 0, 0, 0, 0, 0, 0
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO:0, VI:0, BE:41, BK:0
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO:0:0, VI:0:0, BE:39:0, BK:0:0
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 2
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 58, 58, 58, 58, 58
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO_INNER_DSCP:0, SIG_INNER_DSCP:0, BE_INNER_DSCP:31, OTHER_INNER_DSCP:0,VO_OUTER_DSCP:0, SIG_OUTER_DSCP:0, BE_OUTER_DSCP:31, OTHER_OUTER_DSCP:0
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO_INNER_DSCP:0, SIG_INNER_DSCP:0, BE_INNER_DSCP:39, OTHER_INNER_DSCP:0,VO_OUTER_DSCP:0, SIG_OUTER_DSCP:0, BE_OUTER_DSCP:39, OTHER_OUTER_DSCP:0
2014-May-28, 16:17:53 CEST
INFO
172.16.102.11
Active calls on ''{0}, radio {1}'': {2} 2c:3f:38:5a:b5:70, 2, 0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 0, 0, 0, 0, 0, 0, 0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO:0, VI:0, BE:32, BK:0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO:0:0, VI:0:0, BE:20:1, BK:0:0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, 58, 58, 58, 58, 58
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO_INNER_DSCP:0, SIG_INNER_DSCP:0, BE_INNER_DSCP:16, OTHER_INNER_DSCP:0,VO_OUTER_DSCP:0, SIG_OUTER_DSCP:0, BE_OUTER_DSCP:16, OTHER_OUTER_DSCP:0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
2c:3f:38:5a:b5:70, 2, VO_INNER_DSCP:0, SIG_INNER_DSCP:0, BE_INNER_DSCP:19, OTHER_INNER_DSCP:0,VO_OUTER_DSCP:0, SIG_OUTER_DSCP:0, BE_OUTER_DSCP:19, OTHER_OUTER_DSCP:0
2014-May-28, 16:17:58 CEST
INFO
172.16.102.11
Active calls on ''{0}, radio {1}'': {2} 2c:3f:38:5a:b5:70, 2, 0
Upgrading the Intel drivers to a paket later 16.7 seems to fix the issues, but it's still not nice that this problem is new with this release.