Annual Conference NEXT WEEK - events, reminders, surveys, baseball ... And Wireless Network geektalk

2016-10-21 Thread Brian Helman
Sorry everyone, I'm a little behind schedule this week. I just wanted to get one last email out before the Annual Conference starts next week. This year, the Wireless-LAN group and NETMAN have coordinated sessions to give a (hopefully) consistent presentation/discussion. We have poured over

Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107

2016-10-21 Thread Joachim Tingvold
On 21 Oct 2016, at 15:12, Dennis Xu wrote: You may be hitting this bug for the 105: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuw34201 Fixed in 8.0.135 and later. 107 seems like it may be similarly related to APs hitting a max limit as well. I would consult Tac before upgrading, but seems

RE: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107

2016-10-21 Thread Ian Lyons
If you have *any* 2802 or 1810 devices, I *strongly* urge you to upgrade. That code fork did not work well with the new gear or in my experience redundant (Active/hot standby) controller designs. From: The EDUCAUSE Wireless Issues Constituent Group Listserv

Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107

2016-10-21 Thread Dennis Xu
We see the same issue (code 105) here. Upgraded from 8.0.120 to 8.0.133 with no help. With "show client ap 802.11b AP_name" command, I see a lots of clients in idle state, also these idle clients will not be cleared out by the idle or ARP timeout. I noticed all these clients are