I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. ________________________________ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old "Safe Harbor" release. Here's the doc to it: http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. <[email protected]<mailto:[email protected]>> wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
