WGB will get stuck to an AP

[Jimmy Dhillon]

WGB will get stuck to an AP and then will have to be kicked off of the controller and it joins back again ; no issues. this happens with most Cisco WGBs in a manufacturing environment like ours.

Please any suggestions, list of steps that can be tried to check this.

We had a case open with Cisco TAC for a long time to no avail and now, we want to see what our next steps can be.

@Rasika Nayanajith

[marce1000]

         >..WGB will get stuck to an AP and then will have to be kicked off of the controller and it joins back again 
 - To general a remark for analyzing the issue : provide controller and AP(s) logs when that happens , also include controller model and AP (model(s)) , plus software version being used on the controller , (e.g.)

 M.

[Jimmy Dhillon]

Thanks M for looking into this. Adding more to the context: this WGB is on the crane that will move and thus, it interacts with diffrent APs in the area but all of a sudden this gets stuck to one AP and won't come online. We can see it that is on the controller but for it to function, we have to kick it off and allow it join again. 

WLC : AIR-CT5520-K9

Version running on it : 8.5.182.0

AP (WGB) : I3702, Software version : 15.3(3) JF15

The issue with this is that this cannot be reproduced. I can get more in line information with logs by tomorrow but for now. I am adding logs from the day we had this happen last time; not sure if this will be helpful:

Authentication Aborted for client 6a:33:ef:da:8f:5e Abort Reason:DOT1X RESTARTED DUE TO EAPOL-START/CLIENT ROAM
PreAuth entry is not found for client ce:1e:62:17:ac:38 while processing FT Reassociation request.
Invalid replay counter from client 04:f0:21:90:fd:c7 - got 00 00 00 00 00 00 00 01, expected 00 00 00 00 00 00 00 00
The system has received replay error on slot 0, WLAN ID 5, count 1 from AP dc:ce:c1:72:6b:90
Unable to add wired client 00:30:18:c6:e3:f2.WGB 10:05:ca:2a:71:54. Wired client add may fail as the WGB is not yet in RUN state.

7/10/23 6:44:20.000 PM	72: Jul 10 22:44:14.394: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio1, parent lost: Received disassociate (1) failure
	7/10/23 6:44:20.000 PM	70: Jul 10 18:46:49.056: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio1, parent lost: Received disassociate (1) failure

[marce1000]

   - FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtj57583
             https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtj61260

    Consider using https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.185.0  according to 
                            https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html

 M.

[Jimmy Dhillon]

Thanks M.  I'll go through these links and report back if I have further questions. 

I think it just comes down to OS version which we really can't upgrade given the other challenges that are going to come with it.

[Rich R]

> "I think it just comes down to OS version which we really can't upgrade given the other challenges that are going to come with it."
Hmmm you're on 8.5.182.0 already so you must have had to upgrade at some time not so long ago so it is possible even if difficult.  And you may find the only way to get the fix is to upgrade to the latest version.

I feel your pain on "We had a case open with Cisco TAC for a long time to no avail" - we have 2 similar AP/WLC cases (different issues but also tricky) which TAC just seem to make zero progress on after months - it's hard work getting results from them these days!

[Jimmy Dhillon]

Yes, Rich, I agree. I am currently going through old emails/conversations other team member had with TAC engineers and i am talking about case opened in 2019 (not lying) so, this is some issue. 

Upgrade might solve this issue but it's gonna be a complete project and will happen when we will refresh APs.