To anyone still having this issue: It is a software issue with the 8.2.x.x WLC software and the 2800/3800 series APs.  The APs randomly stop forwarding DHCP requests.  Power cycling the AP fixes it for an unknown amount of time, as it can happen anywhere from 4 hours to 60 days, from my experience. I contacted Cisco TAC and they didn't have a confirmed fix for the issue, but they gave me links (for 5508 and 5520) to software version 8.2.167.6 (not available on the download site), in hopes that the other fixes they had implemented for the 2800/3800 series APs would also fix my issue.  So far, so good.  We're at 25 days without an issue so far. ... View more

Did you ever get this resolved with Cisco TAC?  I am running into the same issue.  Just deployed a few hundred 3802s on 8.2.151, but this also happens on all versions, up to 8.2.166.  I haven't opened a TAC case yet since I wasn't sure what the exact problem was until I came across this post.  But, now I see that the new clients trying to associate are failing to get an DHCP IP address, while those who still have an IP address are working just fine on the same AP.  Rebooting the AP solves the issue for a while, as well.  Thanks! ... View more

Just went to add the app to a coworker's new iPhone and also found it missing.  I sent an email to Cisco's app support team (ac-mobile-feedback@cisco.com) and promptly got this reply: Yesterday we posted an update to correct a couple of issues affecting iOS users. This update checked out correctly in both QA testing and on our Apple Developer site and passed through the necessary App Store approvals. Once AnyConnect physically shows up in the store, it is our practice to immediately test both upgrades and new installs across many devices and iOS versions to ensure everything continues to work flawlessly. Upon immediate testing we noticed that our application was not functioning properly and apparently a portion of our application code disappeared between the Apple Developer site and App Store. At this point the root cause is not yet known (we do not yet know if there is something on our side that needs to be corrected or on Apple's side - we did experience an issue like this once before in 6/2014 and have asked Apple to investigate if this is the same problem or something different). We have had a case open with Apple since yesterday and are awaiting further information from them on their root cause determination. Once the root cause is determined, it is likely that a new version will need to be submitted to them, whether the same exact code with a new version number or after fixing something on our side first if it is determined that an error on our side resulted in this. Unfortunately since the version currently in the app store is truncated/corrupt, the only recourse we had to limit the number of affected end users was to turn off access to AnyConnect. There is no option available to us to revert back to the prior version posted. Since the root cause and solution is not yet known, there is not yet a time estimate for when we will be able to make downloads available again for new installs and to fix users who downloaded in the short period of time when the update was accessible. We apologize for this inconvenience, we are doing everything possible to work with Apple on a root cause and resolution. ... View more

Thank you for posting this!  It saved me from a huge headache!  I had the same problem with some 1532e outdoor access points that weren't connecting to the 5508 controller on 7.6.130.0.  I was getting the following error message in the trap logs: AAA Authentication Failure for UserName:78da6e609f3e User Type: WLAN USER I put the MAC 78:da:6e:60:9f:3e in the MAC Filtering under Security > AAA and the AP was able to connect.   ... View more