Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107
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 like there are a couple active bugs that could be triggering this. 8.0.140 has a long list of resolved caveats that might be worth exploring. 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 inter-controller roaming clients. Then I shuffled some APs among controllers to minimize inter-controller roaming and also use scheduled job from PI to reboot some APs weekly to clear out the idle clients. Now I do not see this error anymore in our environment. If you have inter-controller roaming with AAA override enabled, please also be aware of this bug; https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb21254 We hit it when upgrading to 8.0.140.0, and it only happens when the client roams back the first AP on it’s anchor controller after having roamed to a foreign one. If the client roams further to a new AP on the same anchor controller, it works again (it can even roam back to the first AP it joined, and it will work, so it’s only when hitting that first AP when coming back to your anchor controller). TAC told us that the bug was introduced in versions after 8.0.133.0, and is fixed in escalation build 8.0.140.3. They couldn’t tell us if the bug is affecting other platforms than 5508/WiSM2, so I guess we’ll have to try&fail with our 8540s (-: -- Joachim ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107
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 [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Dennis Xu Sent: Friday, October 21, 2016 9:13 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107 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 inter-controller roaming clients. Then I shuffled some APs among controllers to minimize inter-controller roaming and also use scheduled job from PI to reboot some APs weekly to clear out the idle clients. Now I do not see this error anymore in our environment. Dennis Xu, MASc, CCIE #13056 Analyst 3, Network Infrastructure Computing and Communications Services(CCS) University of Guelph 519-824-4120 Ext 56217 d...@uoguelph.ca<mailto:d...@uoguelph.ca> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> From: The EDUCAUSE Wireless Issues Constituent Group Listserv mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> on behalf of Jake Snyder mailto:jsnyde...@gmail.com>> Sent: Thursday, October 20, 2016 10:25:50 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107 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 like there are a couple active bugs that could be triggering this. 8.0.140 has a long list of resolved caveats that might be worth exploring. Sent from my iPhone On Oct 20, 2016, at 3:15 PM, Legge, Jeffry mailto:jgle...@radford.edu>> wrote: I am see quite a few association errors. Has anyone seen these. I am on 8.0.133.0 ** 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/.
Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107
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 inter-controller roaming clients. Then I shuffled some APs among controllers to minimize inter-controller roaming and also use scheduled job from PI to reboot some APs weekly to clear out the idle clients. Now I do not see this error anymore in our environment. Dennis Xu, MASc, CCIE #13056 Analyst 3, Network Infrastructure Computing and Communications Services(CCS) University of Guelph 519-824-4120 Ext 56217 d...@uoguelph.ca www.uoguelph.ca/ccs From: The EDUCAUSE Wireless Issues Constituent Group Listserv on behalf of Jake Snyder Sent: Thursday, October 20, 2016 10:25:50 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107 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 like there are a couple active bugs that could be triggering this. 8.0.140 has a long list of resolved caveats that might be worth exploring. Sent from my iPhone On Oct 20, 2016, at 3:15 PM, Legge, Jeffry mailto:jgle...@radford.edu>> wrote: I am see quite a few association errors. Has anyone seen these. I am on 8.0.133.0 ** 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/.
Re: [WIRELESS-LAN] WLC Association Failures with reason code 105 and 107
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 like there are a couple active bugs that could be triggering this. 8.0.140 has a long list of resolved caveats that might be worth exploring. Sent from my iPhone > On Oct 20, 2016, at 3:15 PM, Legge, Jeffry wrote: > > I am see quite a few association errors. Has anyone seen these. I am on > 8.0.133.0 > ** 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/.
