Thanks Mike and Loc, The more TAC cases opened for this the better. It's getting the WNBUs attention, and needs to be "checked in" for resolution in the next release (so far looks like they're still trying to isolate the issue -- don't be surprised if they ask you to actively monitor).
The bug as described is exactly what I'm seeing. I see the Decrypt errors in the "sh controller d0 | beg --Clients" output, and there's no issues with Open authentication WLAN clients. 5.2.193 appears immune to this. Reference CSCtf34858 when opening the case. Call early and often. --Bruce Johnson -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Schomer, Michael J. Sent: Wednesday, March 31, 2010 2:45 PM To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade No, we didn't get a fix for it yet, although Cisco says they're working on it. At this point we are pretty sure we are running into bugID CSCtf34858. -Mike -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Pham, Loc Sent: Tuesday, March 30, 2010 11:57 AM To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Mike, do you get the fix for it ? I am ready to call TAC now .... Running to exactly the same issue. Loc -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Schomer, Michael J. Sent: Tuesday, March 23, 2010 6:28 AM To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Disabling dhcp-proxy didn't work for us. After chatting with Cisco I think we are running into BugID CSCte08161 or CSCtf34858. We upgraded to 6.0.196 this morning, which should rule out CSCte08161. Since all the access points rebooted in the process, we probably won't know if it fixed it for a day or so. If not, our solution will probably be to reset the radios every morning, at least until Cisco develops a more permanent solution... and probably a new bug in the process! -Mike -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Charles Spurgeon Sent: Friday, March 19, 2010 5:06 PM To: [email protected] Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking [email protected] / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: > > > 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: > [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra > m_category_home.html > > The test results actually show the test methodolgy, and it's > pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n > s340/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. > <[3][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 > [4]http://www.educause.edu/groups/. > > > ********** Participation and subscription information for this > EDUCAUSE Constituent Group discussion list can be found at > [5]http://www.educause.edu/groups/. > > ********** Participation and subscription information for this > EDUCAUSE Constituent Group discussion list can be found at > [6]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/. > > References > > 1. http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_ho me.html > 2. http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns779/AssureWave-WLC -Release-6.0.196.0-Results.pdf > 3. mailto:[email protected] > 4. http://www.educause.edu/groups/ > 5. http://www.educause.edu/groups/ > 6. 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/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
