Hi Everyone, Thanks for all the interesting insight and troubleshooting attempts.
My colleague is still struggling with this issue and the only benefit thus far is that his android is affected. So thankfully we have a good test candidate. He has been working with TAC and I don't know what debug information he has seen, but I do know that TAC "believes everything is okay and it should work"! Clearly it is not. He cannot associate on an Open SSID, or a Secured SSID with WPA2 AES/PSK. We are not running IPv6, so this was globally disabled already. And the most recent attempt was that we had that changed was Allow AAA Override to become unchecked. This did not resolve the issue either. While I can tolerate a person or two having issues, it is the unknown of how many more are out there who will have issues. We had plans to begin moving buildings using WiSM1 controllers over to the new WiSM2 controllers and I am very reluctant to do that now. I suspect/hope this case will be escalated soon and If we find a solution I will share it with everyone here. In the meantime if you have other ideas, please let me know! Thanks! Daniel Foerst Assistant Director, Networks & Security The Catholic University of America Washington, DC 20064 ________________________________ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [[email protected]] on behalf of Jithin Kesavan [[email protected]] Sent: Tuesday, October 01, 2013 11:04 PM To: [email protected] Subject: Re: [WIRELESS-LAN] Cisco WiSM2 Association issues Hi Daniel, We here at UNSW have been experiencing similar issues for the past few weeks, ever since we upgraded WLC code from 7.2 to 7.5. Basically, what we have found is that this is affecting only Android version 4.1.2 e.g.: Samsung S3 or Galaxy Note 2 etc. Samsung S4 or Galaxy Note 3 running Android 4.2.2 is not affected in our case. We have a mix of different SSIDs. The main one runs 802.1x/WPA2 authenticating against a bunch of radius servers. We have other SSIDs using Web authentication and Pre-shared keys. We even tried on our test SSIDs with open access. Irrespective of the security setting on the WLAN, the device attempts to connect, fails and eventually comes up with "Authentication error occurred". We have a test WiSM2 running 7.2 code. As soon as we move the AP to the test WiSM2, the device can connect without any issues. Last week we raised a TAC request and ran some debug outputs which showed the following: IPv6_Msg_Task: Sep 24 12:01:38.564: 90:18:7c:a8:6b:de Link Local address fe80::9218:7cff:fea8:6bde updated to mscb. Not Advancing pem state.Current state: mscb in apfMsMmInitial mobility state and client state APF_MS_STATE_A *SNMPTask: Sep 24 12:08:04.220: 90:18:7c:a8:6b:de Central Switch = TRUE *SNMPTask: Sep 24 12:08:04.220: 90:18:7c:a8:6b:de Central Switch = TRUE TAC engineer suggested disabling IPv6 globally on the controllers which at the time fixed the issue; only for the issue to resurface after a few days. The only thing is I don't see anything in particular from the debug client <MAC addr> command on the controller. I have re-opened the TAC case, and am waiting for their response. One thing to note is that Android 4.2.2 devices were experiencing similar issues when it was first reported to us, but there was a software update for 4.2 which came sometime in the last month or so, after which the problem seems to have disappeared. Cheers Jithin Jithin Kesavan Senior Network Engineer UNSW IT THE UNIVERSITY OF NEW SOUTH WALES UNSW SYDNEY NSW 2052 AUSTRALIA Phone: +61 2 9385 1154 Mobile: 040 171 3334 Email: [email protected]<mailto:[email protected]> Website: http://www.it.unsw.edu.au<http://www.it.unsw.edu.au/> On 1/10/13 7:05 AM, "Foerst, Daniel P." <[email protected]<mailto:[email protected]>> wrote: Hi all, We are experiencing an odd issue as of late. A client with an Android device (HTC One) is able to associate to a wireless access point joined to a Cisco WiSM1 controller that is running 7.0.235.3 code, but when the AP is joined to a WiSM2 with 7.5.0 code it is unable to join. The most I have heard that it attempts to connect until ultimately it gives up. If the AP is migrated back to a WiSM1 the issue clears and the client is able to associate, receive and IP address, and use the network. The WLAN is an open SSID currently operating without any security so we know that isn't interfering. A TAC case has been opened to investigate this issue, however I wanted to see if anyone else has experienced this yet. Typically I wouldn't give it much thought, but it we have also seen some of our student base experience this same issue with a Windows 8 tablet (not sure if it was RT or not). Where my colleague and his HTC one is able to move the AP back to a WiSM1 and work around the issue, the student doesn't have that luxury as all APs in his/her residence hall are 2602e APs and require a WiSM2 controller. After experiencing this issue we are hesitant to move other residence halls currently operating on WiSM1s to the new WiSM2 controllers. Thanks much! Daniel Foerst Assistant Director, Networks & Security The Catholic University of America Washington, DC 20064 ********** 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/.
