+1. We're also on 7.2.111.3 and wondering if it's time to upgrade. Is there a nice, stable new release for the 5508? I'm still gun shy from the 4400 days, when an upgrade often meant lost weekends and tearing out of hair. John
From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Ball, Erik Sent: Thursday, August 29, 2013 10:17 AM To: [email protected] Subject: Re: [WIRELESS-LAN] What Cisco WLAN controller code are you running? 7.2.111.3 is what we are on, and have stayed there because it has been stable for us. Just wondering if we should jump to 7.4.110.0 or some other code... From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Vikki Cutrone Sent: Thursday, August 29, 2013 10:13 To: [email protected]<mailto:[email protected]> Subject: Re: [WIRELESS-LAN] What Cisco WLAN controller code are you running? I thought this was a bug when Win 8 first came out and fixed in code 7.2.111.3, sometime around October 2012. On Thu, Aug 29, 2013 at 10:06 AM, Ball, Erik <[email protected]<mailto:[email protected]>> wrote: We are curious what Cisco WLAN controller code you are running (5508 controllers?) With the number of Windows 8 systems that are coming in the door from students, we are fairly certain that we are hitting this bug, which we have been resolving with client drivers.... CSCua29504 - 802.11w-capable client fails pairwise key handshake with AES. https://tools.cisco.com/bugsearch/bug/CSCua29504/?referring_site=ss Symptom: An 802.11w-capable client, such as a PC running Windows 8, cannot connect to an SSID using WPA or WPA2 key management with AES encryption. The AP will send the M1 pairwise key message, but the PC will never respond with M2. With "debug client" in effect, a message similar to the following will be seen: *dot1xMsgTask: Jun 12 20:23:37.471: 00:11:22:33:44:55 Retransmit failure for EAPOL-Key M1 to mobile 00:11:22:33:44:55, retransmit count 5, mscb deauth count 0 Conditions: Client is 802.11w-capable, wireless infrastructure is CUWN, SSID using WPA2/AES or WPA/AES. This bug affects CUWN 5.2.178.0 and above, but not CUWN 4.2 or earlier, nor does it affect autonomous IOS APs. Workaround: Use WPA/TKIP or WPA2/TKIP instead. Note that this will limit the client to 802.11g/802.11a data rates. Another workaround is to use a Windows 7, rather than Windows 8 driver, for the adapter. Thanks, Erik ________________________________ "This message may contain confidential and/or proprietary information and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited." ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. -- Vikki Cutrone Network Administrator Vassar College, Box 13 124 Raymond Ave Poughkeepsie, NY 12604-0013 845-437-7231 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ________________________________ "This message may contain confidential and/or proprietary information and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited." ********** 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/.
