Jeff, This ap group bug is fixed in 5.2.193. Actually, a lot of annoying stuff was fixed from 5.2.178 was fixed in 5.2.193, and I'd highly recommend using it instead. 5.2.178 also had several radio bugs (1252 and 1142 APs) and 5.2.193 has corrected them.
Jeff >>> "Legge, Jeffry" <[email protected]> 8/31/2009 10:38 AM >>> I found the cause of my DHCP AP groups problems. When I converted from 4.2 to 5.2.178.0 the ap group interfaces did not get converted and they reverted to the default group. WCS does not allow this to be changed because of a bug. I had to change the ap group interface mapping via the wlc guis. -Jeff Legge Radford University From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Legge, Jeffry Sent: Monday, August 31, 2009 6:56 AM To: [email protected] Subject: Re: [WIRELESS-LAN] 5.2.193 Cisco Controllers- "Freeze Ups"? Lee, I am running 5.2.178 and using AP groups. My clients are getting the default IP address and not the IP address from the AP group (subnet) that they are assigned to. I have an open TAC case. I also had one controller lock up and AP's failed over to other controllers. This was due to having defined a controller in this controller's mobility group that was not online. I removed the entry and the lock up has not re-occurred. FYI. Jeff Legge Radford University From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Lee H Badman Sent: Sunday, August 30, 2009 6:38 PM To: [email protected] Subject: [WIRELESS-LAN] 5.2.193 Cisco Controllers- "Freeze Ups"? Wondering if we're alone in this experience. We had a great opening weekend in that thousands of users got on our secure wireless network with little fanfare. Then tonight, multiple controllers seemed to have simple "frozen" for lack of a better description- all indicators were fine except dhcp renewals and new requests were not getting back to the clients, and established users' traffic stalled. The fix seemed to be moving APs to another controller, booting the one with the stall condition, and moving the APs back. Simply rebooting APs didn't seem to touch it. Anyone experience similar? We've never seen anything like this on past versions. I'm not pointing fingers at the code at this point, but would be curious if anyone else has seen the same sort of problem. Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 ********** 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/.
