It has just come to my attention from Cisco TAC that there are some significatn issues with 126.96.36.199.
I thought that this would be helpful to anyone using this version or considering upgrading to it.
There is supposed to be an emergency release (188.8.131.52) available in the March/April timeframe.
Here is a summary of known bugs in 184.108.40.206:
CSCsh47906 WLC:After upgrade to 220.127.116.11, random AP reloads are observed
CSCsh45987 1020 Series LWAPP access points on Wism controller reboot randomly
CSCsh48977 WLC's IP stack becomes inoperable on a large L2 subnet
CSCsf99924 Daylight savings cannot be set
CSCsh38068 WLAN profile identifier missing from client summary screen and detail
CSCsh38126 WLC virtual interface hostname does not prompt for reboot from CLI CSCsh39110 N Does not allow external antenna for BR1310 in LWAPP mode
CSCsh43557 Cosmetic: Misspelling & miswording in AP Authentication message
CSCsh47269 Upgrade to 4.0 MR2 does not enable broadcast if multicast enabled
CSCsh47364 Enter ? in debug ap command in a telnet/ssh session crash WLC
CSCsh47926 WLC: Serviceability of hardware counters/status
CSCsh49310 A Clear configuration on WLC2006 corrupts image
CSCsh49729 private MIB error of WLC
CSCsh50252 controller is unable to interpret NTP packets correctly
CSCsh50527 NPU Truncates Padding from Unicast ARP Frames
CSCsh50966 WLC does not respond to unicast ARP
Thanks for the heads up. We have been running 18.104.22.168 for almost 2 months now. I haven't noticed the AP's bouncing 1030s w/4404 wlc but good to know. I have needed to restart a ap once in awhile to get clients to connect but that not unique to this version.
The only thing I noticed from a direct result from upgrading was a few of the older wireless cards needed their drivers updated. And I've had a wireless G card that couldn't stay connected. Just kept bouncing. Other then that no real serious issues.
Thanks. That's good info. I've gotten in the habit of opening a TAC case before any WLC upgrade "just in case". I checked the bug toolkit and couldn't find anything for 22.214.171.124 a few weeks ago, but the TAC engineer still said to stay away from it for now. One would hope an image with problems like this would get pulled from the downloads, but I guess that's not the case.
I upgraded to the 126.96.36.199 code about 2 weeks ago, and have not seen any issues. I have 450 AP's running on 4 Controllers, and it looks to be stable at this point
TAC did tell me not to use the 4.0.206 code when I had problems with 188.8.131.52. They gave me file access to the 184.108.40.206 code instead. I had a few controllers randomly become unresponsive to IP traffic. TAC said that there are several bugs for the 220.127.116.11 code for ARP issues.
Any word on when 207 will be available for download? Upgraded to 206 a while back to fix several bugs, and ended up getting more new bugs than were fixed.
dvr0, what type of error messages are you getting? what are some of the critical ones? after this particular post, I am leaning more towards staying with my current release.
I have seen several of the issues listed at the beginning of this post. Right now I have a WISM on 18.104.22.168 that periodically looses connectivity to the 6509 backplane, can't ping and all the AP's drop. I can't access it from the service port either. I discovered if I "shut" and "no shut" the port channel to the WISM, I can then telnet from the 6509 to the WISM's service port and reboot the WISM, if I am quick. The window of connectivity only lasts around 15 seconds. I'm contemplating an upgrade to 22.214.171.124.
I'm running 126.96.36.199 now on 5 WiSM's, things are looking good so far. We used to have the same issue as you with the WiSMN lockup on 188.8.131.52. This upgrade will def fix that issue.
Bit the bullet and upgraded 4 WISM and 3 4404 to 184.108.40.206 late Friday night. Everything went smooth and I think this code is pretty good so far. Fixed the WISM backplane disconnect and the bug # is CSCsf27479.
With the newer releases after 206, Cisco has upped the number of AP's that can concurrently download the new code, so the upgrade process is now much faster.
BTW 220.127.116.11 is now available for download. Going to check it out in the lab, supports TACACS+.