Hi,
This sounds very much like an issue that we had, Cisco got involved, told us repeatedly that it was a client issue, then finally accepted it was a Cisco issue. The bug is CSCtd84852, although it doesn't read like the problem I describe above, I'm assured by our Cisco partner that it's the same bug. I was also told that V7 would address the bug, and that V7 would be released in March, this was in January this year. We rolled back to v4 (despite Cisco telling us it would make no difference) and the problem went away. If you debug a failing client, what do you see? There were a couple of different failing scenarios, but primarily we saw a repeated retransmission of M5 to the client then failure. The controller saw no reply from the client, but it would seem from the air captures we did and supplied to Cisco that the client did respond. Debug client <client MAC> We found that resetting the dot11 interface on the AP cleared the fault for some time, so we implemented a script to detect failed clients on a controller and reset the respective APs. Very messy though. I'll tentatively try v7 on one or two controllers when it's released. Aruba looks very appealing at the minute for our imminent re-procurement, but it could be a case of grass is greener... Cheers, Jezz. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Lee Weers Sent: 18 March 2010 16:03 To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade In doing debug info with cisco tac just resulted in a "It is a client driver issue". Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Schomer, Michael J. Sent: Thursday, March 18, 2010 10:40 AM To: [email protected] Subject: [WIRELESS-LAN] Client DHCP issues after WLC upgrade 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/.
